Triple
T30288961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishar |
E770318
|
entity |
| Predicate | pairedRole |
P74541
|
FINISHED |
| Object | earth counterpart of sky god Anshar |
—
|
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: earth counterpart of sky god Anshar | Statement: [Kishar, pairedRole, earth counterpart of sky god Anshar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedRole Context triple: [Kishar, pairedRole, earth counterpart of sky god Anshar]
-
A.
pairedField
Indicates that one field is logically linked or associated with another field as a corresponding pair.
-
B.
pairedNickname
Indicates that two entities share or are associated with a complementary or matching set of nicknames.
-
C.
pairedSingleWith
chosen
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
D.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6810b25f88190b70300d2c08a345a |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:47 p.m.