Triple
T245945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Ozma |
E5036
|
entity |
| Predicate | dataMedium |
P131
|
FINISHED |
| Object | analog radio data |
—
|
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: analog radio data | Statement: [Project Ozma, dataMedium, analog radio data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataMedium Context triple: [Project Ozma, dataMedium, analog radio data]
-
A.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
B.
mediaMarket
Indicates a relationship where a media outlet or content provider serves, targets, or operates within a particular geographic or demographic market.
-
C.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
D.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
E.
mediaType
chosen
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d128c0081909908825b302ae635 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.