Triple
T15537116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii optical disc |
E370375
|
entity |
| Predicate | readOnly |
P119081
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wii optical disc, readOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readOnly Context triple: [Wii optical disc, readOnly, true]
-
A.
readable
Indicates that one entity can be read or interpreted by another entity (e.g., a subject has permission or ability to read an object).
-
B.
readBy
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
-
C.
readout
Indicates that one entity reports, displays, or outputs the measured or computed value of another entity.
-
D.
reading
Indicates that an entity is engaged in the activity of interpreting and understanding written or printed material from another entity or source.
-
E.
restrictedRight
Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:06 a.m.