Triple
T20462077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludgate (demolished city gate) |
E501949
|
entity |
| Predicate | positionInWall |
P140188
|
FINISHED |
| Object | western gate |
—
|
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: western gate | Statement: [Ludgate (demolished city gate), positionInWall, western gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInWall Context triple: [Ludgate (demolished city gate), positionInWall, western gate]
-
A.
elevationRelativeToWalls
Indicates the vertical position of an entity in relation to the height or level of surrounding walls.
-
B.
positionOnCeiling
Indicates that one entity is located on or attached to the ceiling surface of another entity or space.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOnPillar
Indicates that one entity is located on top of or supported by a pillar.
-
E.
positionInChamber
Indicates the specific location or role an entity holds within a particular chamber or assembly.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a761648190b24cf4bb90a8abb1 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:33 a.m.