Triple
T294224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anatolian languages |
E6057
|
entity |
| Predicate | discoveredThrough |
P7311
|
FINISHED |
| Object | decipherment of Hittite cuneiform tablets |
—
|
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: decipherment of Hittite cuneiform tablets | Statement: [Anatolian languages, discoveredThrough, decipherment of Hittite cuneiform tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredThrough Context triple: [Anatolian languages, discoveredThrough, decipherment of Hittite cuneiform tablets]
-
A.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
discoveryMethod
chosen
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
C.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
D.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
E.
coDiscovererOf
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.