Triple
T5707833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester City Women |
E125828
|
entity |
| Predicate | professionalStatusFromSeason |
P65704
|
FINISHED |
| Object | 2014–15 |
—
|
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: 2014–15 | Statement: [Manchester City Women, professionalStatusFromSeason, 2014–15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionalStatusFromSeason Context triple: [Manchester City Women, professionalStatusFromSeason, 2014–15]
-
A.
professionalLeagueStatus
Indicates that an entity holds official recognition or classification as a professional-level league within its domain.
-
B.
hasProfessionalStatus
Indicates that an entity holds a particular professional standing, rank, or qualification within a field or occupation.
-
C.
careerSeasons
Indicates the number or set of seasons during which an entity actively participated in a particular career or professional role.
-
D.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
E.
officialStatusWithTeam
Indicates that an entity holds or has held an official role, position, or status in relation to a specific team.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024892fd88190a91133fc88365410 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c023dfec6881909ee6189b874b4348 |
completed | March 22, 2026, 5:16 p.m. |
Created at: March 22, 2026, 3:45 p.m.