Triple
T11945942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Miss Golden Eagles |
E284298
|
entity |
| Predicate | hasFormerNickname |
P74525
|
FINISHED |
| Object | Southerners |
—
|
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: Southerners | Statement: [Southern Miss Golden Eagles, hasFormerNickname, Southerners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerNickname Context triple: [Southern Miss Golden Eagles, hasFormerNickname, Southerners]
-
A.
hasHistoricNickname
Indicates that an entity is known by a nickname that has historical significance or longstanding traditional use.
-
B.
formerName
Indicates that an entity was previously known by a different name in the past.
-
C.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
D.
usedAsNicknameSince
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
-
E.
formerAthleticsNickname
chosen
Indicates that an entity was previously known by a particular athletics team nickname that is no longer in current use.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903456ec0819082b8b10755a6b732 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.