Triple
T4617351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECMA-119 |
E100898
|
entity |
| Predicate | targetMedium |
P56966
|
FINISHED |
| Object | CD-ROM XA and related formats |
—
|
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-ROM XA and related formats | Statement: [ECMA-119, targetMedium, CD-ROM XA and related formats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetMedium Context triple: [ECMA-119, targetMedium, CD-ROM XA and related formats]
-
A.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
B.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
C.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
-
D.
basedOnMedium
Indicates that one entity is derived from, adapted from, or created using another entity as its source medium or foundational material.
-
E.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.