Triple
T73369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1Q |
E1468
|
entity |
| Predicate | revises |
P1121
|
FINISHED |
| Object | earlier VLAN tagging practices |
—
|
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: earlier VLAN tagging practices | Statement: [IEEE 802.1Q, revises, earlier VLAN tagging practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revises Context triple: [IEEE 802.1Q, revises, earlier VLAN tagging practices]
-
A.
refit
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
B.
amendedBy
chosen
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
-
E.
advises
Indicates that one entity provides guidance, recommendations, or counsel to 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_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.