Triple
T37163596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVC |
E920738
|
entity |
| Predicate | jointWorkingGroupAbbreviation |
P174583
|
FINISHED |
| Object | JVET |
—
|
NE NERFINISHED |
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: JVET | Statement: [VVC, jointWorkingGroupAbbreviation, JVET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jointWorkingGroupAbbreviation Context triple: [VVC, jointWorkingGroupAbbreviation, JVET]
-
A.
workingGroupAcronym
chosen
Indicates that an entity is identified by, or associated with, the acronym of a specific working group.
-
B.
collaboratesWithAbbreviation
Indicates that one entity works jointly or cooperatively with another entity that is represented in abbreviated form.
-
C.
relatedWorkingGroup
Indicates that there is an associated or connected working group that is relevant to or involved with the referenced entity or activity.
-
D.
affiliationAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of the name of an organization or affiliation.
-
E.
worksWithAbbreviation
Indicates that one entity uses or is associated with a specific abbreviated form of another entity’s name or designation.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.