Triple
T19921099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stag Hunt |
E478795
|
entity |
| Predicate | requiresForHighPayoff |
P100
|
FINISHED |
| Object | mutual cooperation |
—
|
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: mutual cooperation | Statement: [Stag Hunt, requiresForHighPayoff, mutual cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresForHighPayoff Context triple: [Stag Hunt, requiresForHighPayoff, mutual cooperation]
-
A.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiresEarnedIncome
Indicates that something is conditional upon an individual or entity having earned income, such as wages or salary, in order to qualify or apply.
-
C.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
D.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
-
E.
requiresQuality
Indicates that one entity depends on or needs another entity to possess a specific quality or attribute in order for a condition, action, or relationship to hold.
- 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.