Triple
T16622911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danielle Panabaker as Caitlin Snow |
E403875
|
entity |
| Predicate | metahumanStatus |
P123599
|
FINISHED |
| Object | metahuman |
—
|
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: metahuman | Statement: [Danielle Panabaker as Caitlin Snow, metahumanStatus, metahuman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metahumanStatus Context triple: [Danielle Panabaker as Caitlin Snow, metahumanStatus, metahuman]
-
A.
realityStatus
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
-
B.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
C.
mortalStatus
Indicates the state or condition of an entity with respect to being mortal, immortal, or otherwise subject to death.
-
D.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
E.
isHuman
Indicates that the subject entity possesses the defining characteristics or status of being a human.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754f4f508190a5b4b8511623fcd4 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.