Triple
T2683726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumble in the Jungle |
E57432
|
entity |
| Predicate | reasonForTime |
P41485
|
FINISHED |
| Object | to suit US television audiences |
—
|
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: to suit US television audiences | Statement: [Rumble in the Jungle, reasonForTime, to suit US television audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForTime Context triple: [Rumble in the Jungle, reasonForTime, to suit US television audiences]
-
A.
reasonForEvent
Indicates that one event occurs as a consequence of, or is motivated or explained by, another specified cause or reason.
-
B.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
D.
reasonForLocation
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
E.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
- F. None of above. chosen
Provenance (4 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9d7692c81909d8fd9ce3817161b |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.