Triple
T32048786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antrim Round Tower |
E818426
|
entity |
| Predicate | elevationAboveGroundOfEntrance |
P106679
|
FINISHED |
| Object | raised entrance |
—
|
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 entrance | Statement: [Antrim Round Tower, elevationAboveGroundOfEntrance, raised entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAboveGroundOfEntrance Context triple: [Antrim Round Tower, elevationAboveGroundOfEntrance, raised entrance]
-
A.
hasEntranceElevation
chosen
Indicates the elevation at which an entity’s entrance is located, typically measured relative to a reference level such as sea level or ground level.
-
B.
entranceHeight
Indicates the vertical measurement of how tall an entrance is.
-
C.
hasFloorElevation
Indicates that one entity has a specified vertical height or level above a reference point (such as sea level or ground) for its floor.
-
D.
elevationAboveStreet
Indicates the vertical height difference of something relative to the level of the adjacent street.
-
E.
boardingElevation
Indicates the elevation at which boarding occurs for a vehicle or transport facility, typically relative to a standard reference level.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:20 a.m.