Triple
T24722875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. David’s Performance Center |
E612354
|
entity |
| Predicate | clubBasedHere |
P157041
|
FINISHED |
| Object | Austin FC youth teams |
—
|
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: Austin FC youth teams | Statement: [St. David’s Performance Center, clubBasedHere, Austin FC youth teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubBasedHere Context triple: [St. David’s Performance Center, clubBasedHere, Austin FC youth teams]
-
A.
clubBasedHere
chosen
Indicates that a club or organization is based or headquartered at the specified location.
-
B.
communityOrganizations
Indicates that there is an association or involvement between entities and one or more community-based organizations or groups.
-
C.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
D.
hasNearbyCommunity
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
E.
isSuburbanClubOf
Indicates that one club is a suburban branch or affiliate of another, typically located in a suburban area relative to the main or central club.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:41 a.m.