Triple
T5896497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAR |
E131113
|
entity |
| Predicate | introducedAtLevel |
P39395
|
FINISHED |
| Object | top-level professional football |
—
|
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: top-level professional football | Statement: [VAR, introducedAtLevel, top-level professional football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAtLevel Context triple: [VAR, introducedAtLevel, top-level professional football]
-
A.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
B.
introducedDuring
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
C.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
D.
playedAtLevel
chosen
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
E.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.