Triple
T31111860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes Navy Bluejackets football team |
E792967
|
entity |
| Predicate | reasonForProminence |
P56091
|
FINISHED |
| Object | strong rosters |
—
|
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: strong rosters | Statement: [Great Lakes Navy Bluejackets football team, reasonForProminence, strong rosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForProminence Context triple: [Great Lakes Navy Bluejackets football team, reasonForProminence, strong rosters]
-
A.
hasPopularityReason
Indicates that there is a specific reason or factor explaining why something is popular.
-
B.
unitOfProminence
Indicates that one entity specifies the unit or scale in which the prominence or significance of another entity is measured or expressed.
-
C.
reasonForSignificance
chosen
Indicates that one entity explains or justifies why another entity is important, notable, or significant.
-
D.
promotionReason
Indicates the reason or justification for which an entity was promoted to a higher position, status, or level.
-
E.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:04 p.m.