Triple
T6387675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission on International Tables |
E143739
|
entity |
| Predicate | typeOfWorkOverseen |
P1366
|
FINISHED |
| Object | reference work |
—
|
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: reference work | Statement: [Commission on International Tables, typeOfWorkOverseen, reference work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWorkOverseen Context triple: [Commission on International Tables, typeOfWorkOverseen, reference work]
-
A.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
B.
overseesProject
Indicates that one entity has responsibility for supervising, managing, or directing the progress and execution of a project involving another entity.
-
C.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
D.
oversawUnitType
Indicates that an entity had supervisory or managerial responsibility over a particular type or category of unit.
-
E.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06869dfb88190aeb84c6c61414888 |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.