Triple
T32099653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asag |
E819807
|
entity |
| Predicate | typeOfMythologicalBeing |
P54299
|
FINISHED |
| Object | chaos monster |
—
|
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: chaos monster | Statement: [Asag, typeOfMythologicalBeing, chaos monster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMythologicalBeing Context triple: [Asag, typeOfMythologicalBeing, chaos monster]
-
A.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
B.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
hasMythologicalInhabitant
Indicates that a place or location is traditionally believed to be inhabited or occupied by a mythological being or creature.
-
D.
mythologicalCategory
chosen
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
typeOfMythologicalGroup
Indicates that one entity is classified as a specific kind or category of mythological group to which the other entity belongs.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
Created at: May 1, 2026, 12:26 a.m.