Triple
T22938995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC JTC 1/SC 29 |
E569666
|
entity |
| Predicate | usesCollaboration |
P150330
|
FINISHED |
| Object | liaison with ITU-T Study Group 16 |
—
|
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: liaison with ITU-T Study Group 16 | Statement: [ISO/IEC JTC 1/SC 29, usesCollaboration, liaison with ITU-T Study Group 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCollaboration Context triple: [ISO/IEC JTC 1/SC 29, usesCollaboration, liaison with ITU-T Study Group 16]
-
A.
containsCollaboration
Indicates that one entity includes or involves a collaborative relationship or joint activity with another entity.
-
B.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
C.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
D.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
E.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181378660819083239986c846ec17 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:45 p.m.