Triple
T4119156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mach cone |
E90367
|
entity |
| Predicate | occursInMedium |
P54385
|
FINISHED |
| Object | air |
—
|
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: air | Statement: [Mach cone, occursInMedium, air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInMedium Context triple: [Mach cone, occursInMedium, air]
-
A.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
-
B.
introducedInMedium
Indicates that an entity first appears or is initially presented within a specified medium (such as a book, film, game, or other format).
-
C.
basedOnMedium
Indicates that one entity is derived from, adapted from, or created using another entity as its source medium or foundational material.
-
D.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
E.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.