Triple
T26931290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat McBride |
E678227
|
entity |
| Predicate | sport discipline competed in |
P37610
|
FINISHED |
| Object | outdoor soccer |
—
|
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: outdoor soccer | Statement: [Pat McBride, sport discipline competed in, outdoor soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sport discipline competed in Context triple: [Pat McBride, sport discipline competed in, outdoor soccer]
-
A.
competedInDiscipline
chosen
Indicates that an entity took part in a competition or event within a specific discipline or category.
-
B.
sportDisciplineScope
Indicates the specific sport discipline or category within which a given relationship, rule, or activity is defined or applies.
-
C.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
-
D.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
E.
WorldCupDiscipline
Indicates a disciplinary action (such as a card, suspension, or sanction) imposed on an entity in the context of a FIFA World Cup competition.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:12 a.m.