Triple
T31951458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quilín |
E815789
|
entity |
| Predicate | treatyTypeAtLocation |
P20718
|
FINISHED |
| Object | peace agreement |
—
|
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 agreement | Statement: [Quilín, treatyTypeAtLocation, peace agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyTypeAtLocation Context triple: [Quilín, treatyTypeAtLocation, peace agreement]
-
A.
treatyType
chosen
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
-
B.
treatyOrPolicy
Indicates a formal agreement, treaty, or policy that establishes rules, obligations, or guidelines governing the relationship or behavior between entities.
-
C.
treatyFeature
Indicates that one entity is a characteristic, provision, or specific element that forms part of a treaty.
-
D.
treatyArea
Indicates the geographic region or jurisdiction to which a treaty or formal agreement applies.
-
E.
treatyFamily
Indicates that there exists a familial or kinship-based treaty or formal agreement relationship between the entities.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 12:07 a.m.