Triple
T30970312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildcat Branch |
E789075
|
entity |
| Predicate | usedInCaseOf |
P13176
|
FINISHED |
| Object | service diversions between Lowell and Haverhill Lines |
—
|
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: service diversions between Lowell and Haverhill Lines | Statement: [Wildcat Branch, usedInCaseOf, service diversions between Lowell and Haverhill Lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCaseOf Context triple: [Wildcat Branch, usedInCaseOf, service diversions between Lowell and Haverhill Lines]
-
A.
usedInCase
chosen
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
B.
usesCase
Indicates that one entity employs, applies, or makes practical use of another entity for a particular purpose or function.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
developedInCase
Indicates that something (such as a method, argument, or principle) was formulated, articulated, or established within the context of a particular case.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 29, 2026, 8:54 p.m.