Triple
T24163616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gimme Some More |
E598908
|
entity |
| Predicate | isHighEnergyTrack |
P155556
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Gimme Some More, isHighEnergyTrack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighEnergyTrack Context triple: [Gimme Some More, isHighEnergyTrack, true]
-
A.
hasBranchingRatioToHadrons
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
-
B.
isTrackEvent
Indicates that an event is classified as a track-related occurrence, such as a specific action or interaction being recorded for tracking or analytics purposes.
-
C.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
D.
hasMomentumAcceptance
Indicates that a system, device, or configuration allows or supports a specified range or tolerance of momentum values.
-
E.
isTracked
Indicates that an entity’s state, behavior, or presence is being monitored or recorded over time.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:32 p.m.