Triple
T11596917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR-O08 |
E275026
|
entity |
| Predicate | hasAdjacentCodeOnLine |
P100525
|
FINISHED |
| Object | JR-O07 |
—
|
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: JR-O07 | Statement: [JR-O08, hasAdjacentCodeOnLine, JR-O07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentCodeOnLine Context triple: [JR-O08, hasAdjacentCodeOnLine, JR-O07]
-
A.
adjacentLine
Indicates that one line is directly next to another line, sharing a common boundary or position without overlapping.
-
B.
hasAdjacentStationOnLine1
Indicates that one station is directly next to another station along Line 1 in the network.
-
C.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
-
D.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
E.
hasStructureOnOrAdjacent
Indicates that one entity has a physical structure located on it or immediately next to it.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89549c870819086e16e9110bbad87 |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.