Triple
T31479309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The River |
E803092
|
entity |
| Predicate | featuresDemonstrationOf |
P202426
|
FINISHED |
| Object | survival skills |
—
|
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: survival skills | Statement: [The River, featuresDemonstrationOf, survival skills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDemonstrationOf Context triple: [The River, featuresDemonstrationOf, survival skills]
-
A.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
B.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
C.
featuresSign
Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
-
D.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
-
E.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
| PDg | Predicate description generation | batch_6a007ef5f05c8190a2d43e4bc45fba3f |
completed | May 10, 2026, 12:49 p.m. |
Created at: April 30, 2026, 9:31 p.m.