Triple
T31953530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokovian |
E815843
|
entity |
| Predicate | governingDocumentInUniverse |
P15492
|
FINISHED |
| Object | Sokovia Accords |
—
|
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: Sokovia Accords | Statement: [Sokovian, governingDocumentInUniverse, Sokovia Accords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingDocumentInUniverse Context triple: [Sokovian, governingDocumentInUniverse, Sokovia Accords]
-
A.
governingDocumentMentioned
Indicates that a governing document is referenced or cited in relation to the entities involved.
-
B.
universeRule
Indicates a governing principle or law that universally applies across all relevant entities or contexts.
-
C.
governingConvention
chosen
Indicates that one entity is the formal agreement, treaty, or convention that provides the authoritative rules or framework governing another entity or activity.
-
D.
governanceDocumentType
Indicates the specific category or type of formal governance document that defines rules, policies, or oversight for an entity or process.
-
E.
governanceDocumentAuthored
Indicates that a specific governance document was written or created by a particular author or authors.
- 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_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 1, 2026, 12:08 a.m.