Triple
T21075786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moreland |
E519229
|
entity |
| Predicate | isLocatedInQuadrantOfPortland |
P82488
|
FINISHED |
| Object | Southeast |
—
|
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: Southeast | Statement: [Moreland, isLocatedInQuadrantOfPortland, Southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInQuadrantOfPortland Context triple: [Moreland, isLocatedInQuadrantOfPortland, Southeast]
-
A.
situatedInQuarter
chosen
Indicates that one entity is located within or belongs to a specific quarter or district of a larger area.
-
B.
locationOnSquare
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
C.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
D.
locatedNorthwestOf
Indicates that one entity is positioned to the northwest of another entity in space or geography.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d690dc8190839968b562e6b8bb |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:48 p.m.