Triple
T35345341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Central Railroad |
E1020723
|
entity |
| Predicate | lineReuse |
P76380
|
FINISHED |
| Object | Mass Central Rail Trail |
—
|
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: Mass Central Rail Trail | Statement: [Massachusetts Central Railroad, lineReuse, Mass Central Rail Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineReuse Context triple: [Massachusetts Central Railroad, lineReuse, Mass Central Rail Trail]
-
A.
keyReuse
Indicates that the same key is used multiple times, rather than being uniquely generated or dedicated for a single use or context.
-
B.
isReuseOf
Indicates that one entity is derived from, or created by reusing, the content, structure, or components of another entity.
-
C.
lineUse
chosen
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
D.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
E.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.