Triple
T33278874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Redskins football |
E851981
|
entity |
| Predicate | hasNotableAlumniLeague |
P50416
|
FINISHED |
| Object | National Football League |
E2064
|
NE 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: National Football League | Statement: [Miami Redskins football, hasNotableAlumniLeague, National Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAlumniLeague Context triple: [Miami Redskins football, hasNotableAlumniLeague, National Football League]
-
A.
hasNotableSportAlumnus
Indicates that an institution or organization has at least one alumnus who is notable for achievements in sports.
-
B.
hasAlumnusLeague
chosen
Indicates that an educational institution has at least one alumnus who is or was a member of a specified sports league.
-
C.
notableLeague
Indicates that there is a significant or prominent league associated with the subject entity.
-
D.
hasNotableAlumniType
Indicates that an entity has notable alumni belonging to a specified category or type.
-
E.
hasNotableAlumniInstitution
Indicates that an institution is associated with one or more notable alumni who previously attended or graduated from it.
- F. None of above.
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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35390da9708190ab2e0d481db10a5c |
completed | June 19, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: May 1, 2026, 1:32 a.m.