Triple
T15046914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daisy Carter |
E379251
|
entity |
| Predicate | hasStatusInSeries |
P116528
|
FINISHED |
| Object | presumed dead |
—
|
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: presumed dead | Statement: [Daisy Carter, hasStatusInSeries, presumed dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInSeries Context triple: [Daisy Carter, hasStatusInSeries, presumed dead]
-
A.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
C.
hasStatusInText
Indicates that a particular status or state is explicitly mentioned or described within a given text.
-
D.
endOfSeriesStatus
Indicates that a series, sequence, or collection has reached its final state or completion status.
-
E.
seriesStatus
Indicates the current state or phase of a series within its lifecycle (e.g., ongoing, completed, canceled, or planned).
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8e64e48190873104a02a676ff3 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 3 a.m.