Triple
T32894740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rowdies |
E841437
|
entity |
| Predicate | originalNASLFranchiseName |
P91971
|
FINISHED |
| Object | Tampa Bay Rowdies |
E213963
|
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: Tampa Bay Rowdies | Statement: [Rowdies, originalNASLFranchiseName, Tampa Bay Rowdies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNASLFranchiseName Context triple: [Rowdies, originalNASLFranchiseName, Tampa Bay Rowdies]
-
A.
originalNASLPredecessorFounded
Indicates that the subject entity was founded as a predecessor organization to the original NASL (North American Soccer League).
-
B.
currentFranchiseNameSince
Indicates the date or time from which the entity has been operating under its current franchise name.
-
C.
playsForFranchise
Indicates that one entity is an athlete or performer who is a member of, or competes on behalf of, a particular sports franchise or team.
-
D.
hostTeamFranchise
Indicates that a team franchise is serving as the host team in a given game or event.
-
E.
brandContinuityWithNASLClub
chosen
Indicates that a club maintains brand continuity—such as name, logo, or identity—with a former NASL (North American Soccer League) club.
- F. None of above.
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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0205c0bff481908238a382459b3a93 |
completed | May 11, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34d2564014819091aae24afdeb2d35 |
completed | June 19, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a0205143f20819087ee31576835be26 |
completed | May 11, 2026, 4:34 p.m. |
Created at: May 1, 2026, 1:18 a.m.