Triple
T2998389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE5 |
E81124
|
entity |
| Predicate | powerFeeding |
P44924
|
FINISHED |
| Object | transceiver powered from attached station via AUI |
—
|
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: transceiver powered from attached station via AUI | Statement: [10BASE5, powerFeeding, transceiver powered from attached station via AUI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerFeeding Context triple: [10BASE5, powerFeeding, transceiver powered from attached station via AUI]
-
A.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
B.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
C.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
D.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
E.
powerBudget
Indicates the allocated or allowable amount of power that can be used or consumed by an entity or system within specified limits.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.