Triple
T6675514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin FC |
E151839
|
entity |
| Predicate | expansionClub |
P13571
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Austin FC, expansionClub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionClub Context triple: [Austin FC, expansionClub, true]
-
A.
expansionTeamIn
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
B.
expansionFranchiseWith
Indicates a relationship where one entity is an expansion franchise that is formally associated with, derived from, or added to another existing entity (such as a league, organization, or parent franchise).
-
C.
leagueExpansionRelatedTo
Indicates a relationship where one league’s expansion, growth, or addition of teams is connected or relevant to another entity, event, or change.
-
D.
expansionTeamWith
Indicates that one entity is an expansion team associated with, or added to, another entity such as a league, division, or organization.
-
E.
expansionFranchiseClass
chosen
Indicates that an entity is classified as an expansion franchise, typically denoting a team added to a league after its original formation.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c0aa8c5c8190a302b261f11b70cb |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0b6d00819086205b8ce30dd045 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:03 p.m.