Triple
T28901788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone X |
E732967
|
entity |
| Predicate | stereoSpeakers |
P82801
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [iPhone X, stereoSpeakers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stereoSpeakers Context triple: [iPhone X, stereoSpeakers, yes]
-
A.
stereoCapability
Indicates that an entity has the ability to produce, process, or support stereo (two-channel) audio.
-
B.
speakerPosition
Indicates the spatial or contextual location of a speaker relative to other entities or a reference frame during an utterance or event.
-
C.
numberOfSpeakersStatus
Indicates the status or condition of information about how many speakers are involved (e.g., whether the number of speakers is known, estimated, missing, or otherwise qualified).
-
D.
hasStereoOutput
chosen
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
E.
hasNumberOfSpeakersCategory
Indicates a classification of an entity based on the number of speakers associated with it, typically grouping it into predefined size categories.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa8deec8190b1eef143e10c9598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:03 a.m.