Triple
T997973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Zeus at Olympia |
E21537
|
entity |
| Predicate | hasHeightApprox |
P18961
|
FINISHED |
| Object | about 20 meters to the pediment |
—
|
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: about 20 meters to the pediment | Statement: [Temple of Zeus at Olympia, hasHeightApprox, about 20 meters to the pediment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightApprox Context triple: [Temple of Zeus at Olympia, hasHeightApprox, about 20 meters to the pediment]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
hasDimensionsApprox
chosen
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
C.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
D.
heightApproximateFeet
Indicates that one entity’s height is approximately equal to a specified value measured in feet.
-
E.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e2ad9c81908a0f488d3f261fc3 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.