Triple
T2263115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas City Hall |
E50082
|
entity |
| Predicate | hasRecessedSide |
P37534
|
FINISHED |
| Object | south side |
—
|
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: south side | Statement: [Dallas City Hall, hasRecessedSide, south side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecessedSide Context triple: [Dallas City Hall, hasRecessedSide, south side]
-
A.
hasViewingSide
Indicates that one entity serves as the side or surface of another entity that is intended to be viewed or observed.
-
B.
hasApproachSide
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
C.
hasDepartureSide
Indicates the side or direction from which an entity departs or leaves a location.
-
D.
hasBside
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
E.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abc2e97eb0819084acb26cfa4e3946 |
completed | March 7, 2026, 6:17 a.m. |
Created at: March 4, 2026, 7:48 p.m.