Triple
T22829910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC JTC 1/SC 27 |
E565768
|
entity |
| Predicate | workingGroup5Scope |
P22281
|
FINISHED |
| Object | identity management and privacy technologies |
—
|
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: identity management and privacy technologies | Statement: [ISO/IEC JTC 1/SC 27, workingGroup5Scope, identity management and privacy technologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingGroup5Scope Context triple: [ISO/IEC JTC 1/SC 27, workingGroup5Scope, identity management and privacy technologies]
-
A.
workingGroup
Indicates that multiple entities collaborate as a designated team or committee to work together toward a shared task, project, or objective.
-
B.
workScope
chosen
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
C.
collaborationScope
Indicates the extent, boundaries, and areas of responsibility covered by a particular collaboration between entities.
-
D.
relatedWorkingGroup
Indicates that there is an associated or connected working group that is relevant to or involved with the referenced entity or activity.
-
E.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2ac8d48190b6dc7edc5ad82bc7 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.