Triple
T15965195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royals (Upper Darby High School) |
E387168
|
entity |
| Predicate | hasMascotName |
P95748
|
FINISHED |
| Object | Royals |
E387168
|
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: Royals | Statement: [Royals (Upper Darby High School), hasMascotName, Royals]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Royals Context triple: [Royals (Upper Darby High School), hasMascotName, Royals]
-
A.
Royals
Royals is the nickname historically associated with the Rochester Royals, a former professional basketball team that eventually became the Sacramento Kings in the NBA.
-
B.
Royals
The Royals are the athletic teams representing the University of Scranton in NCAA Division III sports.
-
C.
Royals
chosen
Royals is the name of the athletic teams representing Upper Darby High School.
-
D.
Royals
The Royals are the athletic teams representing Queens University of Charlotte in collegiate sports.
-
E.
Royals
Royals is the common short name for the Reading Royals, a professional minor league ice hockey team based in Reading, Pennsylvania.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157258b3c8190a72c868bd055ed94 |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffbe84f4888190b3fdb5f32763f78d |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:54 a.m.