Triple
T4554654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longreads |
E120451
|
entity |
| Predicate | curatesContentFrom |
P57986
|
FINISHED |
| Object | across the web |
—
|
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: across the web | Statement: [Longreads, curatesContentFrom, across the web]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curatesContentFrom Context triple: [Longreads, curatesContentFrom, across the web]
-
A.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
B.
primaryContent
Indicates that one entity serves as the main or most important content associated with another entity.
-
C.
curatedBy
Indicates that something has been selectively organized, managed, or assembled by a particular agent or entity.
-
D.
articleContent
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
E.
curatedAt
Indicates the time or context at which an item was intentionally selected, organized, or assembled as part of a curated collection or set.
- F. None of above. chosen
Provenance (4 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd58127ed08190a04962a43afb888b |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:09 p.m.