Triple
T32740074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CODASYL |
E837194
|
entity |
| Predicate | hadWorkingGroup |
P9939
|
FINISHED |
| Object | CODASYL COBOL Committee |
—
|
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: CODASYL COBOL Committee | Statement: [CODASYL, hadWorkingGroup, CODASYL COBOL Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadWorkingGroup Context triple: [CODASYL, hadWorkingGroup, CODASYL COBOL Committee]
-
A.
workingGroup
chosen
Indicates that multiple entities collaborate as a designated team or committee to work together toward a shared task, project, or objective.
-
B.
hasWorkingGroupReport
Indicates that an entity is associated with, or has produced, a report generated by a working group.
-
C.
hadOrganization
Indicates that an entity was affiliated with, employed by, or otherwise formally associated with a particular organization during some period of time.
-
D.
hasTypeOfWorkingGroup
Indicates that an entity is associated with or classified under a specific type or category of working group.
-
E.
hadMember
Indicates that an entity was formerly a member or part of another entity or 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f717a88190a924d614c2c9bca3 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:12 a.m.