Triple
T5029049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple News |
E113249
|
entity |
| Predicate | curatesFrom |
P57986
|
FINISHED |
| Object | various news publishers |
—
|
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: various news publishers | Statement: [Apple News, curatesFrom, various news publishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curatesFrom Context triple: [Apple News, curatesFrom, various news publishers]
-
A.
curatesContentFrom
chosen
Indicates that one entity selects, organizes, and presents content that originates from another entity.
-
B.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
C.
curatedBy
Indicates that something has been selectively organized, managed, or assembled by a particular agent or entity.
-
D.
curatedAt
Indicates the time or context at which an item was intentionally selected, organized, or assembled as part of a curated collection or set.
-
E.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738f2cc88190a03eebf19e407411 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.