Triple
T664212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Washington Post |
E12822
|
entity |
| Predicate | hasDigitalProduct |
P10200
|
FINISHED |
| Object | The Washington Post app |
—
|
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: The Washington Post app | Statement: [The Washington Post, hasDigitalProduct, The Washington Post app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalProduct Context triple: [The Washington Post, hasDigitalProduct, The Washington Post app]
-
A.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
-
B.
digitalProduct
chosen
Indicates that one entity is a product that exists in digital form or is delivered electronically rather than physically.
-
C.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
D.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
E.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd3d8fc8190866af5c76c08f486 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.