Triple
T590138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE-FL |
E17247
|
entity |
| Predicate | powerBudgetCharacteristic |
P15984
|
FINISHED |
| Object | supports long multimode fiber runs |
—
|
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: supports long multimode fiber runs | Statement: [10BASE-FL, powerBudgetCharacteristic, supports long multimode fiber runs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerBudgetCharacteristic Context triple: [10BASE-FL, powerBudgetCharacteristic, supports long multimode fiber runs]
-
A.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
B.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
C.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
D.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
E.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.