Triple
T25137940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dean of NFL Referees |
E629712
|
entity |
| Predicate | impliesSeniorityIn |
P157963
|
FINISHED |
| Object | NFL officiating |
—
|
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 officiating | Statement: [Dean of NFL Referees, impliesSeniorityIn, NFL officiating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesSeniorityIn Context triple: [Dean of NFL Referees, impliesSeniorityIn, NFL officiating]
-
A.
hasSeniorityStatus
Indicates that one entity holds a particular level or classification of seniority relative to others.
-
B.
hasPermanentSeniority
Indicates that one entity holds a fixed, enduring precedence or higher rank over another that does not change over time.
-
C.
typicalSeniorityLevel
Indicates the usual or most common rank or seniority level associated with an entity in a given context.
-
D.
isTenuredPosition
Indicates that a position is a permanent academic or professional role typically protected from arbitrary dismissal.
-
E.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46600ae608190ae5e662fd4a7e5a5 |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:29 a.m.