Triple
T29545271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hittite kings |
E749612
|
entity |
| Predicate | famousTreaty |
P151714
|
FINISHED |
| Object | Treaty of Kadesh |
—
|
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: Treaty of Kadesh | Statement: [Hittite kings, famousTreaty, Treaty of Kadesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousTreaty Context triple: [Hittite kings, famousTreaty, Treaty of Kadesh]
-
A.
historicalTreaty
Indicates that a formal agreement or pact was established between entities at some point in the past.
-
B.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
C.
treatyAlsoKnownAs
Indicates that a treaty is referred to by an alternative name or alias.
-
D.
notableTreatyDuringReign
chosen
Indicates that a specific treaty is historically notable and occurred during the period of a particular ruler’s reign.
-
E.
treatyName
Indicates the formal name or title assigned to a specific 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cf25fa88190a158d58d32872c01 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 5:06 p.m.