Triple
T8300126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hittite archives |
E194329
|
entity |
| Predicate | storedInAntiquityAs |
P82594
|
FINISHED |
| Object | palace archives |
—
|
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: palace archives | Statement: [Hittite archives, storedInAntiquityAs, palace archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storedInAntiquityAs Context triple: [Hittite archives, storedInAntiquityAs, palace archives]
-
A.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
B.
historicallyStoredGoods
Indicates that an entity has previously stored certain goods at some time in the past.
-
C.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
-
D.
locatedInAncientCity
Indicates that an entity is situated within the boundaries or domain of an ancient city.
-
E.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
- F. None of above. chosen
Provenance (4 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e879c588190a6f95cf7795541ad |
completed | March 31, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:53 p.m.