Triple
T10785676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Dayton (1855) |
E254444
|
entity |
| Predicate | signingParty |
P72844
|
FINISHED |
| Object | representatives of the United States government |
—
|
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: representatives of the United States government | Statement: [Treaty of Dayton (1855), signingParty, representatives of the United States government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingParty Context triple: [Treaty of Dayton (1855), signingParty, representatives of the United States government]
-
A.
signerParty
chosen
Indicates the party that formally signs or executes a document, agreement, or instrument.
-
B.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
C.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
D.
laterSignatory
Indicates that one party signed or agreed to something at a later time than another specified party.
-
E.
nonSignatoryParty
Indicates that an entity is a party related to an agreement or treaty without having formally signed or acceded to it.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d44b488190a9f3ab9b177e737a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.