Triple
T490781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carleton College |
E9983
|
entity |
| Predicate | hasAthleticNickname |
P55
|
FINISHED |
| Object | Knights |
—
|
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: Knights | Statement: [Carleton College, hasAthleticNickname, Knights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAthleticNickname Context triple: [Carleton College, hasAthleticNickname, Knights]
-
A.
athleticsNickname
chosen
Indicates the commonly used nickname or moniker for an entity’s athletics team or sports program.
-
B.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
C.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
D.
knownForSports
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
E.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0e22a308190b04d12974fd08a38 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.