Triple
T27826119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nexus 6 |
E702956
|
entity |
| Predicate | supportsGoogleNow |
P201691
|
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: [Nexus 6, supportsGoogleNow, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGoogleNow Context triple: [Nexus 6, supportsGoogleNow, yes]
-
A.
supportsGooglePlay
Indicates that an entity is compatible with and can run or provide access to Google Play services or applications.
-
B.
supportsVoiceDialing
Indicates that one entity enables or is compatible with initiating phone calls through voice commands for another entity.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportsAlwaysOnHeySiri
Indicates that the subject is capable of continuously listening for and responding to the "Hey Siri" wake phrase without needing to be manually activated.
-
E.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
- F. None of above. chosen
Provenance (4 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
| PDg | Predicate description generation | batch_6a00153fea20819086ff5888bf725d05 |
completed | May 10, 2026, 5:18 a.m. |
Created at: April 27, 2026, 5:52 p.m.