Triple
T31971658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Edge of Night |
E816327
|
entity |
| Predicate | originallyConceivedFor |
P83760
|
FINISHED |
| Object | radio |
—
|
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: radio | Statement: [The Edge of Night, originallyConceivedFor, radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyConceivedFor Context triple: [The Edge of Night, originallyConceivedFor, radio]
-
A.
originallyDevelopedFor
Indicates that something was first created, designed, or produced with the primary purpose of serving a particular use, user group, context, or application.
-
B.
purposeOfOriginalDevelopment
Indicates the original intended purpose or goal for which something was first developed or created.
-
C.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
conceptualizedFor
chosen
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
Created at: May 1, 2026, 12:10 a.m.