Triple
T7107374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Acropolis |
E165620
|
entity |
| Predicate | elevationRelativeToPlaza |
P38218
|
FINISHED |
| Object | raised above the Great Plaza |
—
|
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: raised above the Great Plaza | Statement: [North Acropolis, elevationRelativeToPlaza, raised above the Great Plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRelativeToPlaza Context triple: [North Acropolis, elevationRelativeToPlaza, raised above the Great Plaza]
-
A.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
B.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
C.
elevationFrom
chosen
Indicates a vertical distance relationship where one entity’s height or altitude is measured relative to another reference entity.
-
D.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
E.
elevationToCathedral
Indicates the formal act or process by which a church is raised in status to become a cathedral.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b9f13c8190a14898f241ec17a4 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.