Triple
T18388347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverhawks |
E449652
|
entity |
| Predicate | usesAsTeamName |
P124756
|
FINISHED |
| Object | Anne Arundel Community College athletic programs |
—
|
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: Anne Arundel Community College athletic programs | Statement: [Riverhawks, usesAsTeamName, Anne Arundel Community College athletic programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsTeamName Context triple: [Riverhawks, usesAsTeamName, Anne Arundel Community College athletic programs]
-
A.
usedAsTeamNameUntil
Indicates that an entity served as a team's name up to, but not beyond, a specified point in time.
-
B.
supportsTeamName
Indicates that one entity provides endorsement, backing, or advocacy for a particular team identified by its name.
-
C.
namedForTeam
Indicates that one entity has been given its name in honor of, or derived from, a particular team.
-
D.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
E.
usedAsTeamNameInSeasons
chosen
Indicates that a particular name was used as the official team name during one or more specified seasons.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51840884c81908e84e9206b4739ee |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.