Triple
T24681983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro East |
E611159
|
entity |
| Predicate | hasSportsAffiliationWith |
P67501
|
FINISHED |
| Object | St. Louis City SC |
—
|
NE NERFINISHED |
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: St. Louis City SC | Statement: [Metro East, hasSportsAffiliationWith, St. Louis City SC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsAffiliationWith Context triple: [Metro East, hasSportsAffiliationWith, St. Louis City SC]
-
A.
memberOfSportsOrganization
chosen
Indicates that an entity belongs to or is affiliated with a specific sports organization or club.
-
B.
memberOfSportsLeague
Indicates that an entity is formally part of, or participates as a member in, a specific sports league.
-
C.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
D.
memberOfSportsTeamOwned
Indicates that an entity is a member of a sports team that is owned by another specified entity.
-
E.
memberOfSportsTeamManaged
Indicates that an individual is a member of a sports team that is managed or coached by a specified person or organization.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 3:14 a.m.