Triple
T4753440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonriders of Pern |
E105530
|
entity |
| Predicate | originOfDragons |
P18418
|
FINISHED |
| Object | genetically modified fire-lizards |
—
|
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: genetically modified fire-lizards | Statement: [Dragonriders of Pern, originOfDragons, genetically modified fire-lizards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfDragons Context triple: [Dragonriders of Pern, originOfDragons, genetically modified fire-lizards]
-
A.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
B.
dragon
Indicates that an entity is a dragon or is classified as belonging to the category of dragons.
-
C.
mythologicalGeneration
Indicates a generational relationship in mythology, where one mythological being or group descends from or follows another in a lineage or succession.
-
D.
lionOrigin
Indicates that one entity is the geographical or contextual origin of a lion or group of lions.
-
E.
originSpecies
chosen
Indicates that one entity is the original or source species from which another entity is derived, evolved, or produced.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e72d1c81908eb60960751e52b1 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.