Triple
T30551243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulletin of Kadesh |
E777563
|
entity |
| Predicate | isKeySourceFor |
P49178
|
FINISHED |
| Object | Battle of Kadesh historiography |
—
|
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: Battle of Kadesh historiography | Statement: [Bulletin of Kadesh, isKeySourceFor, Battle of Kadesh historiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeySourceFor Context triple: [Bulletin of Kadesh, isKeySourceFor, Battle of Kadesh historiography]
-
A.
keySourceFor
chosen
Indicates that one entity serves as the primary origin or provider of a key or crucial information used by another entity.
-
B.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
C.
isKeyObservableFor
Indicates that a particular key or identifier can be observed, detected, or monitored within a given context or system.
-
D.
isKeyDependent
Indicates that one entity’s existence, validity, or identification depends on another entity’s key or primary identifier.
-
E.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:20 p.m.