Triple
T28761858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coming Up |
E726135
|
entity |
| Predicate | isPlatformFor |
P17735
|
FINISHED |
| Object | emerging writers |
—
|
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: emerging writers | Statement: [Coming Up, isPlatformFor, emerging writers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlatformFor Context triple: [Coming Up, isPlatformFor, emerging writers]
-
A.
isKeyPlatformFor
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations of another entity.
-
B.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
C.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
D.
consideredPlatform
chosen
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
E.
worksOnPlatform
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:12 a.m.