Triple
T7000206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q-in-Q |
E162316
|
entity |
| Predicate | innerTagRole |
P73503
|
FINISHED |
| Object | identifies customer VLAN |
—
|
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: identifies customer VLAN | Statement: [Q-in-Q, innerTagRole, identifies customer VLAN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innerTagRole Context triple: [Q-in-Q, innerTagRole, identifies customer VLAN]
-
A.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
B.
symbolicRoleOfTarget
Indicates that the target entity serves as a symbolic representation or emblem for another entity or concept.
-
C.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed within a given context.
-
D.
navigationRole
Indicates that one entity serves as a navigational aid, control, or function that helps users move through or orient themselves within another entity (such as an interface, document, or environment).
-
E.
intraPartyRole
Indicates a role or function that an entity holds within a specific political party or internal party structure.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.