Triple
T19921106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stag Hunt |
E478795
|
entity |
| Predicate | hasPayoffProperty |
P23698
|
FINISHED |
| Object | payoff-dominant equilibrium at (stag, 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: payoff-dominant equilibrium at (stag, stag) | Statement: [Stag Hunt, hasPayoffProperty, payoff-dominant equilibrium at (stag, stag)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPayoffProperty Context triple: [Stag Hunt, hasPayoffProperty, payoff-dominant equilibrium at (stag, stag)]
-
A.
hasPayStatus
Indicates the current payment state or condition associated with an entity, such as whether an amount is paid, unpaid, pending, or otherwise resolved.
-
B.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
C.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
D.
payoffProfile
Indicates the mapping from each participant’s choices or strategy combination to the resulting payoffs they receive.
-
E.
hasPaymentModel
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
- 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.