Triple
T25996599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Kings of boxing |
E646502
|
entity |
| Predicate | prominentNetwork |
P61413
|
FINISHED |
| Object | Showtime |
—
|
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: Showtime | Statement: [Four Kings of boxing, prominentNetwork, Showtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentNetwork Context triple: [Four Kings of boxing, prominentNetwork, Showtime]
-
A.
primaryNetwork
chosen
Indicates that one network in a set is designated as the main or default network used for communication or operations.
-
B.
notableOnlinePresence
Indicates that an entity maintains a significant, recognizable, or influential presence in online platforms or digital media.
-
C.
networkOfSpecial
Indicates a relationship where one entity is part of, or connected within, a specialized network or system centered around another entity.
-
D.
networkOfAppearance
Indicates a relationship where entities are connected through shared or co-occurring appearances within the same context, medium, or setting.
-
E.
networkTypePromoted
Indicates that a particular type of network has been elevated, highlighted, or given priority status within a system or 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6056f481c81909fd23b04483b76a0 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:58 a.m.