Triple
T4558695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPCC Chair |
E120541
|
entity |
| Predicate | hasCommitteeScope |
P57661
|
FINISHED |
| Object | policy development |
—
|
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: policy development | Statement: [DPCC Chair, hasCommitteeScope, policy development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommitteeScope Context triple: [DPCC Chair, hasCommitteeScope, policy development]
-
A.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
B.
hasCommitteeFunction
Indicates that a committee is assigned or performs a specific function, role, or responsibility.
-
C.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
-
D.
hasSiblingCommittee
Indicates that one committee is recognized as a sibling committee of another, typically meaning they are parallel or equivalent bodies within the same organizational structure.
-
E.
hasTechnicalCommittee
Indicates that an entity is associated with or overseen by a specific technical committee.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5829cc34819086ad2ae58446502e |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.