Triple
T30359637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hittites |
E772240
|
entity |
| Predicate | scriptDiscoveryDate |
P3836
|
FINISHED |
| Object | early 20th century CE |
—
|
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: early 20th century CE | Statement: [Hittites, scriptDiscoveryDate, early 20th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptDiscoveryDate Context triple: [Hittites, scriptDiscoveryDate, early 20th century CE]
-
A.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
B.
remainsDiscoveredOn
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
-
C.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
D.
archiveDiscovery
Indicates that an entity has uncovered or identified an item, record, or information within an archive or archival collection.
-
E.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:57 p.m.