Triple
T19921102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stag Hunt |
E478795
|
entity |
| Predicate | hasRiskyStrategy |
P137828
|
FINISHED |
| Object | hunt stag |
—
|
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: hunt stag | Statement: [Stag Hunt, hasRiskyStrategy, hunt stag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiskyStrategy Context triple: [Stag Hunt, hasRiskyStrategy, hunt stag]
-
A.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
B.
hasWithdrawalRisk
Indicates that discontinuing or reducing something is associated with a risk of withdrawal effects or adverse reactions.
-
C.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
D.
isHighStakes
Indicates that the situation, event, or decision involves significant risk, consequences, or potential impact, making the outcome particularly critical.
-
E.
hasStrategicPass
Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.