Triple
T22259526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man Controlling Trade (east side) |
E550180
|
entity |
| Predicate | locatedOnSideOfBuilding |
P31095
|
FINISHED |
| Object | east 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: east side | Statement: [Man Controlling Trade (east side), locatedOnSideOfBuilding, east side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfBuilding Context triple: [Man Controlling Trade (east side), locatedOnSideOfBuilding, east side]
-
A.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
C.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
D.
impactSideOfBuilding
Indicates the specific side or face of a building that is affected or struck by an impact.
-
E.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c5b54c8190854690ba599639fa |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.