Triple
T36361045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knowledge Corridor |
E895492
|
entity |
| Predicate | followsExistingLine |
P148835
|
FINISHED |
| Object | Connecticut River Line |
—
|
NE NERFINISHED |
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: Connecticut River Line | Statement: [Knowledge Corridor, followsExistingLine, Connecticut River Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsExistingLine Context triple: [Knowledge Corridor, followsExistingLine, Connecticut River Line]
-
A.
followedLineOf
chosen
Indicates that one entity moved along or traced the same path or trajectory previously taken or defined by another entity.
-
B.
partOfFormerLine
Indicates that something was previously a segment or component of a transportation or service line that no longer exists or operates in its original form.
-
C.
adjacentLine
Indicates that one line is directly next to another line, sharing a common boundary or position without overlapping.
-
D.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
-
E.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:09 p.m.