Triple
T2524866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Shore Line |
E56009
|
entity |
| Predicate | hasLineLength |
P39661
|
FINISHED |
| Object | approximately 90 miles |
—
|
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: approximately 90 miles | Statement: [South Shore Line, hasLineLength, approximately 90 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineLength Context triple: [South Shore Line, hasLineLength, approximately 90 miles]
-
A.
hasNumberOfLines
Indicates the relationship that specifies how many lines are associated with a given entity.
-
B.
hasFieldLength
Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
-
C.
hasLineNumber
Indicates that something is associated with a specific line number, typically denoting its position within an ordered sequence such as lines of text or code.
-
D.
hasMaxLengthApprox
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
-
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. 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd252f1c88190ac93604542f80f49 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1487e0c8190b90dcf30586ad4cd |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:46 p.m.