Triple
T3668595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheriff of London Charity Shield |
E77821
|
entity |
| Predicate | matchStatus |
P10212
|
FINISHED |
| Object | exhibition match |
—
|
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: exhibition match | Statement: [Sheriff of London Charity Shield, matchStatus, exhibition match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchStatus Context triple: [Sheriff of London Charity Shield, matchStatus, exhibition match]
-
A.
matchType
chosen
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
B.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42997d88190bc765559bd7645fc |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.