Triple
T1670538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SW Yamhill Street |
E36113
|
entity |
| Predicate | formsEdgeOf |
P31590
|
FINISHED |
| Object | southern edge of Pioneer Courthouse Square |
—
|
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 edge of Pioneer Courthouse Square | Statement: [SW Yamhill Street, formsEdgeOf, southern edge of Pioneer Courthouse Square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsEdgeOf Context triple: [SW Yamhill Street, formsEdgeOf, southern edge of Pioneer Courthouse Square]
-
A.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
-
B.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
C.
bladeEdge
Indicates that one entity is the cutting edge or sharpened boundary of a blade-related object in relation to another entity.
-
D.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
E.
leafShape
Indicates the characteristic form or outline of a leaf that an entity possesses or exhibits.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab271be3f4819091adcd745dec8159 |
completed | March 6, 2026, 7:12 p.m. |
Created at: March 4, 2026, 7:29 p.m.