Triple
T22204203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlton Athletic Women |
E548760
|
entity |
| Predicate | usesParentClubBadge |
P147288
|
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: [Charlton Athletic Women, usesParentClubBadge, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesParentClubBadge Context triple: [Charlton Athletic Women, usesParentClubBadge, true]
-
A.
usedByClub
Indicates that something (such as a resource, facility, or item) is utilized or employed by a club.
-
B.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
-
C.
isStandOfClub
Indicates that a particular stand or section belongs to, is part of, or is designated for a specific club.
-
D.
supportedClub
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
-
E.
refersToClubIdentity
Indicates that one entity is referencing, invoking, or otherwise making use of the identity, name, or defining characteristics of a particular club.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b25eac4819094b3c50027ed66db |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e723f65c5c8190a0ee3c539e5d0767 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 8:36 p.m.