Triple
T25137943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dean of NFL Referees |
E629712
|
entity |
| Predicate | hasReputationAttribute |
P93104
|
FINISHED |
| Object | respect |
—
|
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: respect | Statement: [Dean of NFL Referees, hasReputationAttribute, respect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationAttribute Context triple: [Dean of NFL Referees, hasReputationAttribute, respect]
-
A.
haveReputation
chosen
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
B.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
C.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
-
D.
hasViewReputation
Indicates that an entity holds a reputation or recognized standing specifically related to viewing, observing, or accessing something.
-
E.
hasInUniverseReputation
Indicates that an entity holds a particular level or type of reputation within a specified fictional or conceptual universe.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 18, 2026, 6:29 a.m.