Triple
T27679579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Washington (1871) |
E697871
|
entity |
| Predicate | arbitrationVenue |
P52146
|
FINISHED |
| Object | Geneva, Switzerland |
—
|
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: Geneva, Switzerland | Statement: [Treaty of Washington (1871), arbitrationVenue, Geneva, Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arbitrationVenue Context triple: [Treaty of Washington (1871), arbitrationVenue, Geneva, Switzerland]
-
A.
arbitrationAwardedTo
Indicates that, as a result of an arbitration process, a decision or award has been granted in favor of a particular party.
-
B.
arbitrationMethod
Indicates the method or procedure used to conduct arbitration between parties in a dispute.
-
C.
divisionArbitratedBy
Indicates that the resolution or allocation of a division (e.g., of assets, responsibilities, or territory) is determined or settled by a specified arbitrating party or authority.
-
D.
courtLocation
Indicates the place or venue where a court proceeding or judicial action takes place.
-
E.
decisionPlace
chosen
Indicates the location where a decision is made or formally determined.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6353654188190915266b42fb1885a |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:46 p.m.