Triple
T30169529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etana of Kish |
E766880
|
entity |
| Predicate | hasCompanionInMyth |
P22642
|
FINISHED |
| Object | eagle |
—
|
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: eagle | Statement: [Etana of Kish, hasCompanionInMyth, eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionInMyth Context triple: [Etana of Kish, hasCompanionInMyth, eagle]
-
A.
hasMagicCompanion
Indicates that an entity is accompanied by or associated with another entity that serves as its magical companion.
-
B.
hasFictionalCompanion
Indicates that one entity has another entity as its fictional companion, typically within a narrative or imaginative context.
-
C.
hasNumberOfCompanions
Indicates the quantity of companions or associates that an entity has.
-
D.
hasCompanionRoleIn
Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
-
E.
companionOf
chosen
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:24 p.m.