Triple
T23770042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London City Lionesses |
E587500
|
entity |
| Predicate | seasonalCompetitionType |
P54920
|
FINISHED |
| Object | league |
—
|
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: league | Statement: [London City Lionesses, seasonalCompetitionType, league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalCompetitionType Context triple: [London City Lionesses, seasonalCompetitionType, league]
-
A.
competesInSeasonalFormat
chosen
Indicates that an entity participates in a competition that is organized into recurring seasons or seasonal formats.
-
B.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
C.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
-
D.
tradeSeason
Indicates a specific period or season during which trading activities or exchanges are allowed, active, or most commonly occur.
-
E.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c465d7948190a4381e39f792a7b4 |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.