Triple
T7000204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q-in-Q |
E162316
|
entity |
| Predicate | headerStructure |
P3703
|
FINISHED |
| Object | outer 802.1Q tag plus inner 802.1Q tag |
—
|
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: outer 802.1Q tag plus inner 802.1Q tag | Statement: [Q-in-Q, headerStructure, outer 802.1Q tag plus inner 802.1Q tag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerStructure Context triple: [Q-in-Q, headerStructure, outer 802.1Q tag plus inner 802.1Q tag]
-
A.
headerFile
Indicates that one file serves as a header file for another file, typically declaring interfaces, types, or constants used by that other file.
-
B.
headerField
chosen
Indicates that one entity is a specific header field (such as a name–value pair) belonging to or defined within another entity, typically a message, request, or document header.
-
C.
headerSize
Indicates the size or length of a header associated with an entity or data structure.
-
D.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
-
E.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0e54c88190b092870f2d128510 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.