Triple
T18024657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ta Keo |
E431213
|
entity |
| Predicate | stateOfConstruction |
P44772
|
FINISHED |
| Object | unfinished |
—
|
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: unfinished | Statement: [Ta Keo, stateOfConstruction, unfinished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfConstruction Context triple: [Ta Keo, stateOfConstruction, unfinished]
-
A.
constructionPhase
chosen
Indicates the specific stage or period an entity is in within an overall construction or building process.
-
B.
stateBuildingProcess
Indicates the process by which governing institutions, administrative structures, and political authority are developed, organized, or strengthened within a state.
-
C.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
D.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
E.
mainConstructionPhaseUnder
Indicates that one construction phase occurs under or is subordinate to another primary construction phase in a project’s timeline or hierarchy.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c554348190bd0df06d0cfe188e |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.