Triple
T30208976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shots |
E768015
|
entity |
| Predicate | usedInCompetitions |
P13690
|
FINISHED |
| Object | National League |
—
|
NE NERFINISHED |
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: National League | Statement: [The Shots, usedInCompetitions, National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCompetitions Context triple: [The Shots, usedInCompetitions, National League]
-
A.
usedInCompetition
chosen
Indicates that something is employed or utilized as part of a competition or contest.
-
B.
usesCompetition
Indicates that one entity employs or leverages another entity as a competitor or within a competitive context.
-
C.
usedInCompetitionContext
Indicates that something is employed or occurs within the setting, rules, or circumstances of a competition or contest.
-
D.
usedOnCompetitionLevel
Indicates that something is applied or valid at a specific level of competition (e.g., local, regional, national, international).
-
E.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 29, 2026, 7:32 p.m.