Triple
T28471699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Soccer Association |
E720455
|
entity |
| Predicate | usedImportedTeams |
P182395
|
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: [United Soccer Association, usedImportedTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedImportedTeams Context triple: [United Soccer Association, usedImportedTeams, true]
-
A.
reasonForImportedTeams
Indicates the underlying cause, purpose, or justification for why the teams were imported.
-
B.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
C.
alsoIncludesTeamsFrom
Indicates that something not only includes its primary elements but additionally encompasses teams originating from another specified group, category, or source.
-
D.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
E.
usesTeamFranchises
Indicates that an entity makes use of, operates through, or is associated with one or more team-based franchise organizations.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 28, 2026, 2:49 a.m.