Triple
T31954106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokovian Accords |
E815857
|
entity |
| Predicate | signingBody |
P14945
|
FINISHED |
| Object | United Nations member 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: United Nations member states | Statement: [Sokovian Accords, signingBody, United Nations member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingBody Context triple: [Sokovian Accords, signingBody, United Nations member states]
-
A.
signatureElement
Indicates that one entity is a component or part of another entity’s signature, such as a defining element within a formal or identifying representation.
-
B.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
-
C.
signingStandard
Indicates that an entity conforms to, uses, or is governed by a particular standard or specification for signing (e.g., digital signatures or formal approvals).
-
D.
signText
Indicates that a sign bears or displays a particular textual content.
-
E.
signatoryBloc
chosen
Indicates that an entity is a member of, or aligned with, a specific bloc or group that has jointly signed or endorsed an agreement, treaty, or document.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:08 a.m.