Triple
T25666159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Blue Soccer |
E643521
|
entity |
| Predicate | ownsClubType |
P19215
|
FINISHED |
| Object | professional women’s soccer club |
—
|
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: professional women’s soccer club | Statement: [Sky Blue Soccer, ownsClubType, professional women’s soccer club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownsClubType Context triple: [Sky Blue Soccer, ownsClubType, professional women’s soccer club]
-
A.
refersToClubType
chosen
Indicates that one entity is associated with or designates a particular type or category of club.
-
B.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
-
C.
associatedClubSport
Indicates that there is a relationship between a club and the sport with which it is connected or aligned.
-
D.
representedClub
Indicates that an entity has acted as a representative of, or played for, a particular club or team.
-
E.
associatedClub1
Indicates that an entity has a primary or first-listed association with a particular club 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb2e5e548190a0b3a84b02c07940 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:04 p.m.