Triple
T27658038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC JTC 1/SC 22 |
E697044
|
entity |
| Predicate | workingGroupFor |
P149840
|
FINISHED |
| Object | Fortran programming language standardization |
—
|
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: Fortran programming language standardization | Statement: [ISO/IEC JTC 1/SC 22, workingGroupFor, Fortran programming language standardization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingGroupFor Context triple: [ISO/IEC JTC 1/SC 22, workingGroupFor, Fortran programming language standardization]
-
A.
workingGroup
Indicates that multiple entities collaborate as a designated team or committee to work together toward a shared task, project, or objective.
-
B.
relatedWorkingGroup
Indicates that there is an associated or connected working group that is relevant to or involved with the referenced entity or activity.
-
C.
workingGroupRole_SA4
Indicates that an entity holds a specific role or position within working group SA4.
-
D.
workingGroupRole_SA2
Indicates that an entity holds a specific role or responsibility within the SA2 working group.
-
E.
hasTypeOfWorkingGroup
chosen
Indicates that an entity is associated with or classified under a specific type or category of working group.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:35 p.m.