Triple
T10083589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Bay Rowdies |
E213963
|
entity |
| Predicate | originalNASLPredecessorFounded |
P91970
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Tampa Bay Rowdies, originalNASLPredecessorFounded, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNASLPredecessorFounded Context triple: [Tampa Bay Rowdies, originalNASLPredecessorFounded, 1975]
-
A.
seasonCountInNASL
Indicates the number of seasons an entity participated in the NASL (North American Soccer League).
-
B.
foundedAsFranchiseYear
Indicates the year in which an entity was established specifically as a franchise.
-
C.
teamFoundedAs
Indicates the original name or identity under which a team was first established or created.
-
D.
team1Established
Indicates that the first team in a given context has been founded or formally established.
-
E.
teamFoundedLegacy
Indicates that a team was established as a continuation, successor, or legacy of a prior organization or team.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04352d081908f676444cd2d2578 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9 p.m.