Triple
T17788954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome Boger |
E444099
|
entity |
| Predicate | hasRefereed |
P128835
|
FINISHED |
| Object | NFL playoff games |
—
|
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: NFL playoff games | Statement: [Jerome Boger, hasRefereed, NFL playoff games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefereed Context triple: [Jerome Boger, hasRefereed, NFL playoff games]
-
A.
peerReviewed
Indicates that a work, study, or submission has been evaluated and critiqued by qualified experts in the same field before acceptance or publication.
-
B.
hasReferees
chosen
Indicates that an entity is associated with one or more referees who oversee, judge, or validate its activities or events.
-
C.
isCitedFor
Indicates that one entity references another as a source of information, evidence, or authority for a specific claim, idea, or contribution.
-
D.
refereedCompetition
Indicates that a competition is overseen by an official referee or judging authority who enforces rules and makes binding decisions.
-
E.
hasRefereesFrom
Indicates that an entity is officiated or overseen by referees originating from a specified source or location.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879524bc819090855ab5248c73db |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.