Triple
T15537148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii optical disc |
E370375
|
entity |
| Predicate | readMethod |
P119085
|
FINISHED |
| Object | laser optical pickup |
—
|
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: laser optical pickup | Statement: [Wii optical disc, readMethod, laser optical pickup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readMethod Context triple: [Wii optical disc, readMethod, laser optical pickup]
-
A.
readBy
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
-
B.
readsFrom
Indicates that one entity obtains or accesses data, information, or content from another entity as a source.
-
C.
readBehavior
Indicates that one entity engages in the act or manner of reading something, capturing how that reading is performed or characterized.
-
D.
readReturns
Indicates that an entity returns or provides the result or output of a read operation on another entity.
-
E.
readIn
Indicates that an entity reads or studies something within a particular location or context.
- 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.