Triple
T9041041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnin’ Train |
E216626
|
entity |
| Predicate | hasPhysicalAvailability |
P53051
|
FINISHED |
| Object | CD |
—
|
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: CD | Statement: [Burnin’ Train, hasPhysicalAvailability, CD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalAvailability Context triple: [Burnin’ Train, hasPhysicalAvailability, CD]
-
A.
hasPhysicalMedium
chosen
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
B.
initialAvailability
Indicates the starting level or state of availability of an entity before any changes or updates occur.
-
C.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
D.
hasPhysicalControl
Indicates that one entity currently exercises direct, tangible control or possession over another entity or object.
-
E.
hasPhysicalFootprint
Indicates that one entity occupies or affects a specific physical area or space in the real world.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b100a348190a59abd6e9b815c63 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.