Triple
T73305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3af |
E1467
|
entity |
| Predicate | classificationMethod |
P859
|
FINISHED |
| Object | power class levels |
—
|
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: power class levels | Statement: [IEEE 802.3af, classificationMethod, power class levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationMethod Context triple: [IEEE 802.3af, classificationMethod, power class levels]
-
A.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
B.
researchClassification
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
-
C.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
D.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
E.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
- F. None of above.
Provenance (3 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a252201fa481908e30791954119c17 |
completed | Feb. 28, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69a24eacfdc481909e9ff99752fd42bf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.