Triple
T28556493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOU Raiders |
E723020
|
entity |
| Predicate | hasCoedTeams |
P201032
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SOU Raiders, hasCoedTeams, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoedTeams Context triple: [SOU Raiders, hasCoedTeams, yes]
-
A.
hasAdultTeams
Indicates that the subject is associated with one or more teams composed of adult participants.
-
B.
hasIndependentTeams
Indicates that an entity possesses or is associated with teams that operate autonomously from other teams or central control.
-
C.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
D.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
E.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
- F. None of above. chosen
Provenance (4 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
| PDg | Predicate description generation | batch_69ffc3eed97c819085c06ffe3699ff38 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 28, 2026, 3:46 a.m.