Triple
T37224154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Beeper |
E922961
|
entity |
| Predicate | runsFasterThan |
P66402
|
FINISHED |
| Object | most other Tiny Toon Adventures characters |
—
|
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: most other Tiny Toon Adventures characters | Statement: [Little Beeper, runsFasterThan, most other Tiny Toon Adventures characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsFasterThan Context triple: [Little Beeper, runsFasterThan, most other Tiny Toon Adventures characters]
-
A.
runsTheLengthOf
Indicates that one entity extends continuously alongside or across the full distance of another entity.
-
B.
racesAgainst
Indicates that one entity competes in a race directly against another entity.
-
C.
fasterThan
chosen
Indicates that one entity moves, operates, or progresses at a higher speed than another entity.
-
D.
canOutrun
Indicates that one entity is able to run faster than another and thus surpass or escape it in a running context.
-
E.
legRunner
Indicates that an entity functions as a runner or moving component that operates in conjunction with a leg or leg-like structure.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.