Triple
T30357525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hi-MD |
E772187
|
entity |
| Predicate | dataRewritability |
P93404
|
FINISHED |
| Object | rewritable medium |
—
|
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: rewritable medium | Statement: [Hi-MD, dataRewritability, rewritable medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRewritability Context triple: [Hi-MD, dataRewritability, rewritable medium]
-
A.
writable
chosen
Indicates that one entity has permission or capability to modify or write data to another entity.
-
B.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
-
C.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
D.
laterRewrittenAs
Indicates that an earlier work, version, or expression was subsequently rewritten or replaced by a later one.
-
E.
likelyWrittenFrom
Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823fe8c48190a8911627f79dd949 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:57 p.m.