Triple
T19921101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stag Hunt |
E478795
|
entity |
| Predicate | hasSafeOutcome |
P55064
|
FINISHED |
| Object | both players hunt hare |
—
|
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: both players hunt hare | Statement: [Stag Hunt, hasSafeOutcome, both players hunt hare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafeOutcome Context triple: [Stag Hunt, hasSafeOutcome, both players hunt hare]
-
A.
safetyOutcome
chosen
Indicates the resulting condition or consequence related to safety that arises from an action, event, or situation.
-
B.
failsSafeTo
Indicates that one entity does not successfully ensure the safety or protection of another entity or context.
-
C.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
D.
hasProposedOutcome
Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
-
E.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c564788190a3893fc73fc4922b |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.