Triple
T32041186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin |
E818222
|
entity |
| Predicate | speciesStatusInStory |
P141134
|
FINISHED |
| Object | rare |
—
|
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: rare | Statement: [Kevin, speciesStatusInStory, rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesStatusInStory Context triple: [Kevin, speciesStatusInStory, rare]
-
A.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
B.
speciesStatus
chosen
Indicates the conservation or population status assigned to a species, such as whether it is endangered, threatened, or of least concern.
-
C.
endangeredStatusInStory
Indicates that an entity is portrayed as endangered or at risk within the context of a particular story or narrative.
-
D.
stateInFiction
Indicates that a particular state or condition exists within a fictional context or narrative world rather than in real-world actuality.
-
E.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 12:19 a.m.