Triple
T37706251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonehenge Phase I ditch and bank |
E939205
|
entity |
| Predicate | constructionPhaseOf |
P44772
|
FINISHED |
| Object | Stonehenge Phase I |
—
|
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: Stonehenge Phase I | Statement: [Stonehenge Phase I ditch and bank, constructionPhaseOf, Stonehenge Phase I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionPhaseOf Context triple: [Stonehenge Phase I ditch and bank, constructionPhaseOf, Stonehenge Phase I]
-
A.
constructionPhase
chosen
Indicates the specific stage or period an entity is in within an overall construction or building process.
-
B.
constructionState
Indicates the current phase or status of progress in a construction or building process.
-
C.
capitalPhase
Indicates a relationship where an entity is in a particular stage or phase of capital development, investment, or funding.
-
D.
developmentPhaseName
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.