Triple
T7099440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USC Trojans baseball |
E165415
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Trojans |
E176693
|
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: Trojans | Statement: [USC Trojans baseball, nickname, Trojans]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trojans Context triple: [USC Trojans baseball, nickname, Trojans]
-
A.
Trojans
The Trojans were the inhabitants of the ancient city of Troy, famed in Greek mythology for their decade-long struggle against the Greeks in the legendary Trojan War.
-
B.
Trojans
The Trojans are the athletic teams that represent Troy University in collegiate sports competitions.
-
C.
Trojans
chosen
The Trojans are the athletic teams representing the University of Southern California in collegiate sports.
-
D.
Trojans
The Trojans are the athletic teams representing the University of Arkansas at Little Rock in collegiate sports competitions.
-
E.
Trojan
Trojan is the athletics nickname and mascot representing the sports teams of Trinidad State College.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e58531c88190a32746f9a97da709 |
completed | March 27, 2026, 8:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c79ca6236c81908a7051bd00d0ca90 |
completed | March 28, 2026, 9:17 a.m. |
Created at: March 27, 2026, 2:42 p.m.