Triple
T32445123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BKN |
E829121
|
entity |
| Predicate | associatedJunctionStatus |
P149251
|
FINISHED |
| Object | junction station |
—
|
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: junction station | Statement: [BKN, associatedJunctionStatus, junction station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedJunctionStatus Context triple: [BKN, associatedJunctionStatus, junction station]
-
A.
hasJunctionStatus
chosen
Indicates the status or condition of a junction within a system or network.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
D.
associationStatus
Indicates the current state or condition of an established association or relationship between entities.
-
E.
junctionType
Indicates the specific kind or configuration of a junction that relates connected elements or paths.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:55 a.m.