Triple
T28264213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old Reader |
E712656
|
entity |
| Predicate | supportsDataExportFormat |
P79861
|
FINISHED |
| Object | OPML |
—
|
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: OPML | Statement: [The Old Reader, supportsDataExportFormat, OPML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataExportFormat Context triple: [The Old Reader, supportsDataExportFormat, OPML]
-
A.
canExportToFormat
chosen
Indicates that something has the capability to be exported or converted into a specified file or data format.
-
B.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
-
C.
dataExportOffered
Indicates that an entity makes data available for export to another party or system.
-
D.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
E.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: April 27, 2026, 11:13 p.m.