Triple
T27994875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Gate |
E706983
|
entity |
| Predicate | directionRelativeToFortress |
P73279
|
FINISHED |
| Object | southern 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: southern entrance | Statement: [South Gate, directionRelativeToFortress, southern entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionRelativeToFortress Context triple: [South Gate, directionRelativeToFortress, southern entrance]
-
A.
directionFromCitadel
Indicates the spatial direction or orientation of one entity as measured outward from a citadel.
-
B.
directionRelativeTo
chosen
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
C.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
D.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
E.
directionFromParkCenter
Indicates the compass direction or relative bearing of an entity when measured outward from the center point of a park.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 7:52 p.m.