Triple
T31747744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G01 |
E810317
|
entity |
| Predicate | adjacentCodeEast |
P180900
|
FINISHED |
| Object | G02 |
—
|
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: G02 | Statement: [G01, adjacentCodeEast, G02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentCodeEast Context triple: [G01, adjacentCodeEast, G02]
-
A.
adjacentCodeDirectionWest
Indicates that one code element is positioned immediately to the west (left) of another code element.
-
B.
adjacentTimeZoneEast
Indicates that one time zone is directly to the east of another, sharing a common boundary without any intervening time zones.
-
C.
directionEastSide
Indicates that one entity is located on or oriented toward the eastern side of another entity.
-
D.
neighboringSuburbEast
Indicates that one suburb is directly to the east of, and adjacent to, another suburb.
-
E.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 30, 2026, 11:27 p.m.