Triple
T18081494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellie |
E432699
|
entity |
| Predicate | speciesStatusInUniverse |
P58920
|
FINISHED |
| Object | prehistoric animal |
—
|
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: prehistoric animal | Statement: [Ellie, speciesStatusInUniverse, prehistoric animal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesStatusInUniverse Context triple: [Ellie, speciesStatusInUniverse, prehistoric animal]
-
A.
speciesInUniverse
Indicates that a given species exists within, or is a member of, a particular fictional or defined universe.
-
B.
hasInUniverseInhabitants
Indicates that a universe or fictional setting contains certain beings or populations as its inhabitants.
-
C.
speciesNameInUniverse
Indicates that a given name is the designated species name within a particular fictional or defined universe.
-
D.
in-universeStatus
chosen
Indicates the canonical status or role that something holds within the fictional universe or narrative continuity itself.
-
E.
inUniverseOwnerSpecies
Indicates that a particular species is recognized as the canonical or in-universe owner of something within a fictional or defined universe.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9fb42888190919fe711a281bd7c |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:27 a.m.