Triple
T3043623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unfinished Obelisk |
E83188
|
entity |
| Predicate | constructionPhase |
P44772
|
FINISHED |
| Object | rough shaping completed |
—
|
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: rough shaping completed | Statement: [Unfinished Obelisk, constructionPhase, rough shaping completed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionPhase Context triple: [Unfinished Obelisk, constructionPhase, rough shaping completed]
-
A.
mainConstructionPhaseUnder
Indicates that one construction phase occurs under or is subordinate to another primary construction phase in a project’s timeline or hierarchy.
-
B.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
C.
constructionProgram
Indicates that an entity is involved in or associated with a program or plan for constructing, building, or developing something.
-
D.
constructionTime
Indicates the duration or specific point in time required to construct or build an entity.
-
E.
constructionType
Indicates the specific method or style by which something is built or constructed.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b5ec5988190b8b6c95c743c6d1e |
completed | March 8, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.