Triple
T8266032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Kadesh |
E193303
|
entity |
| Predicate | concludedInCentury |
P10339
|
FINISHED |
| Object | 13th century BCE |
—
|
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: 13th century BCE | Statement: [Treaty of Kadesh, concludedInCentury, 13th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludedInCentury Context triple: [Treaty of Kadesh, concludedInCentury, 13th century BCE]
-
A.
endedInCentury
chosen
Indicates that an event, period, or process concluded during a specified century.
-
B.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
C.
incorporatedInCentury
Indicates that an entity (such as an organization or company) was formally incorporated during a specified century.
-
D.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
E.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794c54448190a685b8d0070980d7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:50 p.m.