Triple
T37887758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Major Major Major |
E945044
|
entity |
| Predicate | nameMotivation |
P7885
|
FINISHED |
| Object | joke about military rank |
—
|
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: joke about military rank | Statement: [Major Major Major Major, nameMotivation, joke about military rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameMotivation Context triple: [Major Major Major Major, nameMotivation, joke about military rank]
-
A.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
B.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
motivationKeyword
Indicates that a keyword or phrase expresses the underlying motivation or driving reason associated with an entity or action.
-
D.
characterMotivation
Indicates the underlying reasons, desires, or goals that drive a character’s actions and decisions within a narrative.
-
E.
laterMotivation
Indicates that one event, state, or action serves as a motivation or reason for another event, state, or action that occurs later in time.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.