Triple
T16983671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessica Riley |
E412005
|
entity |
| Predicate | canSurviveInGame |
P21744
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jessica Riley, canSurviveInGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSurviveInGame Context triple: [Jessica Riley, canSurviveInGame, true]
-
A.
survivesIn
chosen
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
B.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
-
C.
canDieIn
Indicates that one entity is capable of dying, ceasing to exist, or being destroyed within, because of, or in the context of another entity or situation.
-
D.
isGameAnimalIn
Indicates that an entity is considered a game animal within a specified location or jurisdiction.
-
E.
hasSurvivabilityFeature
Indicates that an entity possesses a characteristic, design element, or capability intended to enhance its ability to endure, resist damage, or remain functional under adverse conditions.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d188ede48190baead48aac84c78d |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.