Triple
T1852110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurrian |
E41617
|
entity |
| Predicate | hasImportantCorpus |
P32304
|
FINISHED |
| Object | Hittite archives at Hattusa |
—
|
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: Hittite archives at Hattusa | Statement: [Hurrian, hasImportantCorpus, Hittite archives at Hattusa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantCorpus Context triple: [Hurrian, hasImportantCorpus, Hittite archives at Hattusa]
-
A.
hasLimitedCorpus
Indicates that the associated entity possesses only a small or restricted set of available data, texts, or examples for use or analysis.
-
B.
corpus
chosen
Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
-
C.
primaryCorpusType
Indicates the main or dominant type or category of corpus associated with an entity.
-
D.
hasCorpusType
Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
-
E.
hasSignificantLanguage
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.