Triple
T6428110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayton Agreement |
E128109
|
entity |
| Predicate | definedStateStructure |
P35320
|
FINISHED |
| Object | two-entity structure of Bosnia and Herzegovina |
—
|
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: two-entity structure of Bosnia and Herzegovina | Statement: [Dayton Agreement, definedStateStructure, two-entity structure of Bosnia and Herzegovina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedStateStructure Context triple: [Dayton Agreement, definedStateStructure, two-entity structure of Bosnia and Herzegovina]
-
A.
stateStructureContext
chosen
Indicates the contextual framework or structural conditions of a state within which a given relationship or action occurs.
-
B.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
C.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
D.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
E.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06922a27881908c5571f2aa31e0c1 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.