Triple
T38302270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAO Programme Committee |
E1032250
|
entity |
| Predicate | hasWorkingDocument |
P142847
|
FINISHED |
| Object | Programme of Work and Budget |
—
|
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: Programme of Work and Budget | Statement: [FAO Programme Committee, hasWorkingDocument, Programme of Work and Budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingDocument Context triple: [FAO Programme Committee, hasWorkingDocument, Programme of Work and Budget]
-
A.
hasWorkingBody
Indicates that an entity possesses a functional, operational physical body.
-
B.
hasWorkForm
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
-
C.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
D.
hasDOC
chosen
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
-
E.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:30 p.m.