Triple
T38366910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Mendoza |
E892472
|
entity |
| Predicate | originCityInUniverse |
P86009
|
FINISHED |
| Object | Jacksonville |
unclear NED1
|
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: Jacksonville | Statement: [Jason Mendoza, originCityInUniverse, Jacksonville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCityInUniverse Context triple: [Jason Mendoza, originCityInUniverse, Jacksonville]
-
A.
homeTownInUniverse
Indicates that a location is the character’s hometown within a specified fictional or defined universe.
-
B.
cityOfFictionalOrigin
chosen
Indicates the city from which a fictional character, entity, or work is described as originating within its narrative or fictional universe.
-
C.
basedInUniverseCity
Indicates that an entity is located or primarily situated within the fictional setting known as Universe City.
-
D.
cityOfOriginal
Indicates the city from which something or someone originally comes or was first created or established.
-
E.
inUniverseBirthplace
Indicates that an entity’s birthplace is located within a specified fictional or defined universe.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7e947b081908757acfb80fa3bc4 |
completed | June 28, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.