Triple
T8384748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Watney |
E197785
|
entity |
| Predicate | usesSkill |
P39122
|
FINISHED |
| Object | botany to grow food on Mars |
—
|
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: botany to grow food on Mars | Statement: [Mark Watney, usesSkill, botany to grow food on Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSkill Context triple: [Mark Watney, usesSkill, botany to grow food on Mars]
-
A.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
B.
killsByProxy
Indicates that one entity causes the death of another entity indirectly through an intermediary or agent rather than committing the act personally.
-
C.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
D.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
E.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e03eb08190a458c9caa0524e0f |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.