Triple
T18401582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFP |
E450008
|
entity |
| Predicate | hasBureausIn |
P68855
|
FINISHED |
| Object | many countries worldwide |
—
|
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: many countries worldwide | Statement: [AFP, hasBureausIn, many countries worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBureausIn Context triple: [AFP, hasBureausIn, many countries worldwide]
-
A.
examplesOfBureaus
Indicates that the related entities are specific bureau instances that serve as examples of the referenced bureau category or type.
-
B.
hasPoliticalBureau
Indicates that an entity possesses or is associated with a political bureau as part of its organizational or governance structure.
-
C.
hasBranchOffice
chosen
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
D.
hasAssociatedOffice
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
E.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the specified place.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5195185b08190bd3b5471cdc047b0 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.