Triple
T73347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1Q |
E1468
|
entity |
| Predicate | tagProtocolIdentifier |
P3331
|
FINISHED |
| Object | 0x8100 |
—
|
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: 0x8100 | Statement: [IEEE 802.1Q, tagProtocolIdentifier, 0x8100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagProtocolIdentifier Context triple: [IEEE 802.1Q, tagProtocolIdentifier, 0x8100]
-
A.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
-
B.
usedInProtocol
chosen
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
C.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
D.
pennantNumber
Indicates the identifying pennant number assigned to a ship or naval vessel.
-
E.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
- 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.