Triple
T35009376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariposa Military Base |
E1009903
|
entity |
| Predicate | locatedInUniverseRegion |
P99968
|
FINISHED |
| Object | California |
E1909002
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: California | Statement: [Mariposa Military Base, locatedInUniverseRegion, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInUniverseRegion Context triple: [Mariposa Military Base, locatedInUniverseRegion, California]
-
A.
hasInUniverseLocationRelation
Indicates a relationship where an entity is associated with, or situated at, a specific location within a fictional or defined universe or setting.
-
B.
inUniverseRegion
chosen
Indicates that an entity is located within or belongs to a specific universe-defined region or area.
-
C.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
D.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
E.
builtLocationInUniverse
Indicates that a construction or structure was created or established at a specific location within a particular universe or cosmic setting.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bd1800e081908bff91c63ec91a78 |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.