Triple
T7951153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ink Master |
E184616
|
entity |
| Predicate | competitionFormatIncludes |
P2673
|
FINISHED |
| Object | elimination challenges |
—
|
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: elimination challenges | Statement: [Ink Master, competitionFormatIncludes, elimination challenges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionFormatIncludes Context triple: [Ink Master, competitionFormatIncludes, elimination challenges]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
C.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
D.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
E.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5b7450819091e4e6f21e9d832d |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:10 p.m.