Triple
T17593499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winged Beaver |
E428503
|
entity |
| Predicate | isMythical |
P128141
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Winged Beaver, isMythical, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMythical Context triple: [Winged Beaver, isMythical, true]
-
A.
isMythologicalFigureType
Indicates that one entity is classified as a specific type or category of mythological figure in relation to another entity.
-
B.
isMythicPrototypeOf
Indicates that one entity serves as the mythic or legendary archetype, model, or original form upon which the other entity is based or derived.
-
C.
hasMythicalFigure
Indicates that one entity is associated with, features, or includes a particular mythical or legendary figure.
-
D.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
E.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
- F. None of above. chosen
Provenance (4 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e89acc81908e52138ad4f452c6 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:51 a.m.