Triple
T29358202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelly Gibbs |
E744505
|
entity |
| Predicate | inUniverseLifeStatus |
P173396
|
FINISHED |
| Object | died as a child |
—
|
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: died as a child | Statement: [Kelly Gibbs, inUniverseLifeStatus, died as a child]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseLifeStatus Context triple: [Kelly Gibbs, inUniverseLifeStatus, died as a child]
-
A.
inUniverseSocialStatus
Indicates the social rank or standing an entity holds within a specific fictional or defined universe.
-
B.
inUniverseActivity
Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
-
C.
inUniverseFamily
Indicates that one entity is a family member of another within the same fictional or narrative universe.
-
D.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
E.
inUniverseUser
Indicates that a user exists or participates within a specified fictional or conceptual universe.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 2:14 p.m.