Triple
T22524166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niamey Convention |
E556856
|
entity |
| Predicate | signatoryCharacteristic |
P148714
|
FINISHED |
| Object | French-speaking states |
—
|
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: French-speaking states | Statement: [Niamey Convention, signatoryCharacteristic, French-speaking states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatoryCharacteristic Context triple: [Niamey Convention, signatoryCharacteristic, French-speaking states]
-
A.
signatureFeature
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
B.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
C.
signaturePersona
Indicates that an entity serves as the primary or defining persona, identity, or character most closely associated with another entity.
-
D.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
E.
signatureConcept
Indicates that one concept is the defining or characteristic idea that most distinctly represents or identifies another concept.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e34590c81909e4ed1c95f13a199 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:51 p.m.