Triple
T28264212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old Reader |
E712656
|
entity |
| Predicate | supportsDataImportFormat |
P8463
|
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, supportsDataImportFormat, OPML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataImportFormat Context triple: [The Old Reader, supportsDataImportFormat, OPML]
-
A.
canImportFormat
chosen
Indicates that an entity has the capability to import or read data in a specified format.
-
B.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
-
C.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
D.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
E.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
- 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_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: April 27, 2026, 11:13 p.m.