Triple
T1027179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metroon of Olympia |
E22164
|
entity |
| Predicate | presentCondition |
P24157
|
FINISHED |
| Object | ruined |
—
|
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: ruined | Statement: [Metroon of Olympia, presentCondition, ruined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentCondition Context triple: [Metroon of Olympia, presentCondition, ruined]
-
A.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
B.
precondition
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
C.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
D.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
E.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7276180819085c6b23501a6a6e0 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b95bb5908190ad1d5f5e0d8f664d |
completed | March 1, 2026, 10:10 p.m. |
Created at: March 1, 2026, 7:41 p.m.