Triple
T20796709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Absent-Minded Professor |
E511929
|
entity |
| Predicate | usesFlubberFor |
P100686
|
FINISHED |
| Object | enhancing basketball performance |
—
|
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: enhancing basketball performance | Statement: [The Absent-Minded Professor, usesFlubberFor, enhancing basketball performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFlubberFor Context triple: [The Absent-Minded Professor, usesFlubberFor, enhancing basketball performance]
-
A.
hasFluid
Indicates that one entity contains, holds, or is associated with a particular fluid.
-
B.
fliesWith
Indicates that one entity travels through the air in the company of, or using the same aircraft or flying means as, another entity.
-
C.
usableInAir
Indicates that an entity can function or be operated effectively while in the air.
-
D.
usesPowerFor
chosen
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
E.
canFlyViaFlame
Indicates that an entity is capable of flying by using or generating flame as the means of propulsion or lift.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2ad6f0481909e0bab7119f10f9c |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.