Triple
T14010622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildcats |
E337067
|
entity |
| Predicate | representsTeamsOf |
P15218
|
FINISHED |
| Object | Jasper High School students |
—
|
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: Jasper High School students | Statement: [Wildcats, representsTeamsOf, Jasper High School students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsTeamsOf Context triple: [Wildcats, representsTeamsOf, Jasper High School students]
-
A.
representsTeamsNamed
Indicates that two or more entities are associated with teams that share the same name.
-
B.
representsTeamFrom
Indicates that an entity serves as the representative team originating from or associated with a particular place, organization, or group.
-
C.
teamRepresentation
Indicates that one entity serves as the official representative or embodiment of a team in a given context or activity.
-
D.
representedByTeam
chosen
Indicates that an entity is officially or formally represented by a specific team.
-
E.
representsInLeague
Indicates that an entity serves as a representative of another entity within a specific league or organized competition.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed5cfd0819085b9c860b119a9de |
completed | April 14, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.