Triple
T19234707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3x |
E480962
|
entity |
| Predicate | usesAddress |
P1216
|
FINISHED |
| Object | reserved multicast address for MAC control frames |
—
|
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: reserved multicast address for MAC control frames | Statement: [IEEE 802.3x, usesAddress, reserved multicast address for MAC control frames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAddress Context triple: [IEEE 802.3x, usesAddress, reserved multicast address for MAC control frames]
-
A.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
B.
canAddress
Indicates that one entity has the ability or permission to direct communication, action, or service toward another entity.
-
C.
usesAddressingSystem
chosen
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
D.
usesMailingAddressOf
Indicates that one entity uses another entity’s mailing address as its own for receiving mail or official correspondence.
-
E.
helpsAddress
Indicates that one entity contributes to solving, mitigating, or dealing with an issue, need, or problem associated with another entity.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faeb53988190b83afee9974058c6 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.