Triple
T6428085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brčko District |
E128108
|
entity |
| Predicate | hasArbitrationAwardDate |
P70826
|
FINISHED |
| Object | 5 March 1999 |
—
|
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: 5 March 1999 | Statement: [Brčko District, hasArbitrationAwardDate, 5 March 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArbitrationAwardDate Context triple: [Brčko District, hasArbitrationAwardDate, 5 March 1999]
-
A.
awardedDate
Indicates the date on which an award, prize, or honor was formally given to an entity.
-
B.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
C.
arguedDate
Indicates the date on which an argument, debate, or legal case was formally presented or argued.
-
D.
awardedSince
Indicates that an entity has been receiving a particular award continuously from a specified starting time onward.
-
E.
appealDate
Indicates the date on which an appeal is formally filed, recorded, or scheduled in relation to a decision or case.
- 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_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. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:44 p.m.