Triple
T28400329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synchronous Digital Hierarchy |
E719378
|
entity |
| Predicate | hasOverheadType |
P164459
|
FINISHED |
| Object | section 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: section overhead | Statement: [Synchronous Digital Hierarchy, hasOverheadType, section overhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverheadType Context triple: [Synchronous Digital Hierarchy, hasOverheadType, section overhead]
-
A.
hasOverload
Indicates that an entity defines multiple variants (overloads) of the same operation or function, typically distinguished by differing parameters or signatures.
-
B.
typicalOverhead
Indicates the usual or expected amount of additional cost, time, or resource usage associated with performing an action or maintaining a relationship.
-
C.
hasOverheadCatenary
Indicates that an object or infrastructure segment is equipped with an overhead catenary system for supplying electric power.
-
D.
hasOverheadStructures
Indicates that one entity possesses or includes structural elements positioned above or spanning over another area or object.
-
E.
hasOverflowBehavior
Indicates that an entity specifies how it behaves when its capacity or limit is exceeded (i.e., what happens on overflow).
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d6a679881909445372a0d5f75c4 |
completed | May 2, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 1:19 a.m.