Triple
T27230443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tawakoni people |
E682138
|
entity |
| Predicate | treatyPartyOf |
P6785
|
FINISHED |
| Object | Treaties with the Republic of Texas |
—
|
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: Treaties with the Republic of Texas | Statement: [Tawakoni people, treatyPartyOf, Treaties with the Republic of Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyPartyOf Context triple: [Tawakoni people, treatyPartyOf, Treaties with the Republic of Texas]
-
A.
partnerInTreaty
chosen
Indicates that an entity is a formal participant or signatory in a specific treaty or international agreement.
-
B.
recognizedByTreatyParty
Indicates that an entity’s status, rights, or existence is formally acknowledged or accepted by a party to a treaty under the terms of that treaty.
-
C.
treatyConcludedBy
Indicates that a treaty was formally agreed upon, finalized, or brought into effect by a specified party or parties.
-
D.
wasSignatoryOf
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
-
E.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 9:46 a.m.