Triple
T35528367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenian–Croatian border |
E1026730
|
entity |
| Predicate | arbitrationStatus |
P110269
|
FINISHED |
| Object | Croatia rejected arbitration award |
—
|
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: Croatia rejected arbitration award | Statement: [Slovenian–Croatian border, arbitrationStatus, Croatia rejected arbitration award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arbitrationStatus Context triple: [Slovenian–Croatian border, arbitrationStatus, Croatia rejected arbitration award]
-
A.
disputeStatus
chosen
Indicates the current state or condition of a disagreement or conflict between parties.
-
B.
arbitration
Indicates a relationship where a neutral third party is formally empowered to resolve a dispute between other parties and issue a binding or advisory decision.
-
C.
arbitrationAwardedTo
Indicates that, as a result of an arbitration process, a decision or award has been granted in favor of a particular party.
-
D.
negotiationStatus
Indicates the current state or phase of an ongoing or completed negotiation between parties.
-
E.
arbitrationMethod
Indicates the method or procedure used to conduct arbitration between parties in a dispute.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.