Triple
T28869864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syracuse men's tennis team |
E732111
|
entity |
| Predicate | representedInstitutionNicknameHistory |
P29026
|
FINISHED |
| Object | Orangemen |
E198766
|
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: Orangemen | Statement: [Syracuse men's tennis team, representedInstitutionNicknameHistory, Orangemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedInstitutionNicknameHistory Context triple: [Syracuse men's tennis team, representedInstitutionNicknameHistory, Orangemen]
-
A.
associatedInstitutionNickname
chosen
Indicates that an institution is commonly known or referred to by a particular nickname.
-
B.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
C.
associatedWithStadiumNickname
Indicates that an entity is connected to or commonly referred to by a particular stadium nickname.
-
D.
teamNicknamedAfter
Indicates that a team is commonly referred to by a nickname derived from or inspired by another entity.
-
E.
historicalNameOfInstitution
Indicates that one institution is a former or historical name by which another institution was previously known.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d3fabe5c819088a22bd89d3a0c0c |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 7:31 a.m.