Triple
T9845899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadling Country |
E239340
|
entity |
| Predicate | hasPeaceStatus |
P43581
|
FINISHED |
| Object | largely free from conflict |
—
|
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: largely free from conflict | Statement: [Quadling Country, hasPeaceStatus, largely free from conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeaceStatus Context triple: [Quadling Country, hasPeaceStatus, largely free from conflict]
-
A.
typeOfPeace
chosen
Indicates a relationship where one entity specifies or classifies the particular kind or category of peace associated with another entity.
-
B.
maintainedPeaceWith
Indicates that two entities sustained a state of peace or non-conflict with each other over a period of time.
-
C.
hasNationalStatus
Indicates that an entity possesses an official national-level designation, recognition, or status within a country.
-
D.
peaceTerms
Indicates the conditions or agreements proposed or accepted by parties to establish or maintain peace after or during a conflict.
-
E.
hasPeacekeepingComponent
Indicates that something includes, involves, or is associated with a peacekeeping-related element, unit, or function.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35ff7848190a8a717773d8654b9 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.