Triple
T37660052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series 30 |
E937696
|
entity |
| Predicate | doesNotPrimarilySupport |
P101700
|
FINISHED |
| Object | smartphone applications |
—
|
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: smartphone applications | Statement: [Series 30, doesNotPrimarilySupport, smartphone applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotPrimarilySupport Context triple: [Series 30, doesNotPrimarilySupport, smartphone applications]
-
A.
doesNotPrimarilyProvide
chosen
Indicates that one entity does not mainly or chiefly supply, offer, or furnish a particular service, resource, or function to another entity.
-
B.
doesNotPrimarilyUse
Indicates that the subject entity does not mainly or predominantly employ, rely on, or make use of the specified object or method.
-
C.
doesNotPrimarilyAddress
Indicates that something fails to mainly focus on, deal with, or concern a particular topic, issue, or entity.
-
D.
doesNotPrimarilyContain
Indicates that one entity does not have another entity as its main or predominant component, element, or content.
-
E.
doNotSupport
Indicates that one entity withholds help, approval, or endorsement from another entity or action.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.