Triple
T10132392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Hanlon |
E226369
|
entity |
| Predicate | callsLosersBackDuring |
P92150
|
FINISHED |
| Object | 1985 events in It |
—
|
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: 1985 events in It | Statement: [Mike Hanlon, callsLosersBackDuring, 1985 events in It]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callsLosersBackDuring Context triple: [Mike Hanlon, callsLosersBackDuring, 1985 events in It]
-
A.
loserReceives
Indicates that the entity who loses in a contest, game, or comparison is the one that receives a specified item, outcome, or consequence.
-
B.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
C.
opponentDuringRetreat
Indicates that one entity serves as the opposing force or adversary of another entity during the latter’s retreat.
-
D.
loserPoints
Indicates the number of points awarded to or accumulated by the losing side in a competitive event or comparison.
-
E.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd336cbf48190b647c69675d0b06f |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:06 p.m.