Triple
T2056408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Irvin |
E45683
|
entity |
| Predicate | receptions |
P35491
|
FINISHED |
| Object | 750 |
—
|
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: 750 | Statement: [Michael Irvin, receptions, 750]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receptions Context triple: [Michael Irvin, receptions, 750]
-
A.
reception
Indicates the act of receiving or welcoming someone or something, often marking the initial acknowledgment or acceptance in an interaction or process.
-
B.
laterReception
Indicates that one entity receives or accepts something at a time that is later than when another related reception or event occurs.
-
C.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
D.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
E.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9abdb088190991a620e01dc226f |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb92f90a881909a1f10b060132a9e |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:40 p.m.