Triple
T37464413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumble Run |
E930997
|
entity |
| Predicate | hasBossCount |
P100152
|
FINISHED |
| Object | 8 encounters per full run (approximate) |
—
|
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: 8 encounters per full run (approximate) | Statement: [Rumble Run, hasBossCount, 8 encounters per full run (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBossCount Context triple: [Rumble Run, hasBossCount, 8 encounters per full run (approximate)]
-
A.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
B.
hasCentralBoss
Indicates that an entity is under the authority or control of a primary, central boss figure.
-
C.
hasBossForm
Indicates that an entity has a special, typically more powerful "boss" version or transformation form.
-
D.
hasBossType
Indicates that one entity functions as the superior or boss type in relation to another entity.
-
E.
numberOfBosses
chosen
Indicates the count of distinct boss or supervisor entities associated with a given entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:17 p.m.