Triple
T20866374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.ST |
E513772
|
entity |
| Predicate | trackContribution |
P142160
|
FINISHED |
| Object | scratching on "Rockit" |
—
|
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: scratching on "Rockit" | Statement: [D.ST, trackContribution, scratching on "Rockit"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackContribution Context triple: [D.ST, trackContribution, scratching on "Rockit"]
-
A.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
B.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
C.
trackUsed
Indicates that a particular track (such as a route, path, or media track) has been utilized or selected in a given context.
-
D.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
E.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c460807c8190a337d8cc6c7b1438 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:45 p.m.