Triple
T23408788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maguan |
E560007
|
entity |
| Predicate | treatyTypeAssociated |
P20718
|
FINISHED |
| Object | peace treaty |
—
|
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: peace treaty | Statement: [Maguan, treatyTypeAssociated, peace treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyTypeAssociated Context triple: [Maguan, treatyTypeAssociated, peace treaty]
-
A.
treatyType
chosen
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
-
B.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
C.
treatyFamily
Indicates that there exists a familial or kinship-based treaty or formal agreement relationship between the entities.
-
D.
relatedToTreaty
Indicates that there exists a connection, association, or relevance between an entity and a specific treaty or treaties.
-
E.
linkedTreaty
Indicates that there is a formal treaty connection or association between the related entities, such as being parties to, or otherwise bound by, the same treaty.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.