Triple
T14674257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympieion |
E344595
|
entity |
| Predicate | hasConstructionHistory |
P110244
|
FINISHED |
| Object | long and complex |
—
|
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: long and complex | Statement: [Olympieion, hasConstructionHistory, long and complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionHistory Context triple: [Olympieion, hasConstructionHistory, long and complex]
-
A.
hasProductionHistory
Indicates that an entity is associated with a record or account of its past production activities, processes, or outputs.
-
B.
hasStructureHistory
chosen
Indicates that there exists a record or account detailing the past states, changes, or development of a structure over time.
-
C.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5666e648190b5faa07076f497b8 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.