Triple
T25534586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AZW |
E640008
|
entity |
| Predicate | readableBy |
P18381
|
FINISHED |
| Object | Kindle desktop apps |
—
|
NE NERFINISHED |
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: Kindle desktop apps | Statement: [AZW, readableBy, Kindle desktop apps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readableBy Context triple: [AZW, readableBy, Kindle desktop apps]
-
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.
canBeReadWith
Indicates that one entity is suitable or compatible to be read or interpreted together with another entity.
-
C.
canRead
Indicates that one entity has the ability or permission to read or access the content of another entity.
-
D.
readPubliclyIn
Indicates that an entity performs a reading of something (e.g., a text or work) in a public setting or context.
-
E.
readBy
chosen
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f866376081909ab76a8aa5c3fea7 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 3:16 p.m.