Triple
T19450927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Special Event September 2017 |
E486611
|
entity |
| Predicate | presentationLanguage |
P3681
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Apple Special Event September 2017, presentationLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentationLanguage Context triple: [Apple Special Event September 2017, presentationLanguage, English]
-
A.
presentation
Indicates that one entity formally shows, explains, or demonstrates something (such as information, ideas, or a product) to an audience or another entity.
-
B.
presentationLevel
Indicates the degree or intensity with which something is presented, displayed, or made perceptible in a given context.
-
C.
presentationContext
Indicates the situational setting or environment in which a presentation, display, or communication of something takes place.
-
D.
presentationMoment
Indicates the specific time or occasion at which something is formally presented or delivered.
-
E.
presentedInLanguage
chosen
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.