Triple
T29679250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman–Kushite War |
E750905
|
entity |
| Predicate | peaceNegotiatedAt |
P47375
|
FINISHED |
| Object | Samos |
—
|
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: Samos | Statement: [Roman–Kushite War, peaceNegotiatedAt, Samos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peaceNegotiatedAt Context triple: [Roman–Kushite War, peaceNegotiatedAt, Samos]
-
A.
peaceAccordDate
Indicates the date on which a formal peace accord between parties was signed or came into effect.
-
B.
peaceSignedAt
chosen
Indicates that a formal peace agreement was signed at a specific location.
-
C.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
D.
peaceConcludedUnder
Indicates that a peace agreement or treaty was formally established under specified conditions, authority, or circumstances.
-
E.
ceasefireDate
Indicates the date on which a ceasefire between parties is formally initiated, agreed, or comes into effect.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 7:09 p.m.