Triple
T7876958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAF Women’s Champions League |
E182879
|
entity |
| Predicate | includesTitleHolder |
P1911
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CAF Women’s Champions League, includesTitleHolder, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTitleHolder Context triple: [CAF Women’s Champions League, includesTitleHolder, yes]
-
A.
hasTitleHolder
chosen
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
refersToTitleHolder
Indicates that one entity makes reference to, or designates, the entity that currently holds a specific title or position.
-
D.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
E.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39bc07208190aa452cef8ca5b0d6 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.