Triple
T38590705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miqo'te |
E932445
|
entity |
| Predicate | hasStartingCityStateOptions |
P22794
|
FINISHED |
| Object | Gridania |
—
|
NE NERFINISHED |
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: Gridania | Statement: [Miqo'te, hasStartingCityStateOptions, Gridania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartingCityStateOptions Context triple: [Miqo'te, hasStartingCityStateOptions, Gridania]
-
A.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
-
B.
startCity
chosen
Indicates the city where a journey, route, or transportation service begins.
-
C.
hasEndCities
Indicates that something, typically a route or connection, is associated with specific cities at its endpoints.
-
D.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
E.
containsCityState
Indicates that one entity includes or encompasses a specific city and state within its scope or boundaries.
- F. None of above.
Provenance (3 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: May 3, 2026, 4:32 p.m.