Triple
T28540493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady of the kings and queens |
E722277
|
entity |
| Predicate | appliedToDeityIn |
P71453
|
FINISHED |
| Object | Hittite religion |
—
|
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 religion | Statement: [Lady of the kings and queens, appliedToDeityIn, Hittite religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToDeityIn Context triple: [Lady of the kings and queens, appliedToDeityIn, Hittite religion]
-
A.
appliesToDeityIn
chosen
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
-
B.
offeredToDeity
Indicates that something is presented or dedicated as an offering to a deity.
-
C.
involvesDeity
Indicates that the situation, event, or concept has the participation, presence, or relevance of a deity as a central element of the relationship.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
targetedDeity
Indicates that an action, event, or entity is specifically directed toward or aimed at a particular deity.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 28, 2026, 3:35 a.m.