Triple
T28470850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-1 |
E720431
|
entity |
| Predicate | hasLineOverhead |
P185633
|
FINISHED |
| Object | SONET line overhead |
—
|
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: SONET line overhead | Statement: [STS-1, hasLineOverhead, SONET line overhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineOverhead Context triple: [STS-1, hasLineOverhead, SONET line overhead]
-
A.
hasOverheadType
Indicates that one entity is associated with a specific category or type of overhead (such as cost, resource, or operational overhead) that applies to it.
-
B.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
C.
hasLines
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
D.
hasOverheadCatenary
Indicates that an object or infrastructure segment is equipped with an overhead catenary system for supplying electric power.
-
E.
hasLineLength
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 28, 2026, 2:48 a.m.