Triple
T5867788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Home Championship |
E130438
|
entity |
| Predicate | sharedTitlesAllowed |
P67592
|
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: [British Home Championship, sharedTitlesAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedTitlesAllowed Context triple: [British Home Championship, sharedTitlesAllowed, yes]
-
A.
sharesTitleWith
Indicates that two entities have the same title or name.
-
B.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
C.
authorizedByTitle
Indicates that an action or permission is granted based on a person’s role, position, or formal title rather than on individual identity.
-
D.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c044fe17d08190b9bf47b13863ef52 |
completed | March 22, 2026, 7:37 p.m. |
Created at: March 22, 2026, 3:56 p.m.