Triple
T16126711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taikazan |
E391290
|
entity |
| Predicate | locationOnField |
P121570
|
FINISHED |
| Object | central area of the Kok-boru field |
—
|
LITERAL 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: central area of the Kok-boru field | Statement: [Taikazan, locationOnField, central area of the Kok-boru field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnField Context triple: [Taikazan, locationOnField, central area of the Kok-boru field]
-
A.
locationOnSquare
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
B.
locationFormed
Indicates the place or geographic area where an entity (such as an organization, group, or structure) was originally established or came into existence.
-
C.
locationOnKit
Indicates that an entity is located on or attached to a specific kit or equipment set.
-
D.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
E.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
- F. None of above. chosen
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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20204fb408190b58d49d0d64bb740 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.