Triple
T2944872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixel 4a |
E79475
|
entity |
| Predicate | fingerprintSensor |
P17643
|
FINISHED |
| Object | rear-mounted capacitive |
—
|
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: rear-mounted capacitive | Statement: [Pixel 4a, fingerprintSensor, rear-mounted capacitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fingerprintSensor Context triple: [Pixel 4a, fingerprintSensor, rear-mounted capacitive]
-
A.
hasFingerprintSensor
chosen
Indicates that an entity is equipped with or includes a fingerprint recognition sensor.
-
B.
hasFaceUnlock
Indicates that an entity supports or is equipped with a facial recognition–based unlocking feature.
-
C.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
D.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
E.
hasSecurityTerminal
Indicates that an entity is equipped with or contains a security terminal used for access control, monitoring, or security-related operations.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b2752481908ec6f9a9cc24c0a7 |
completed | March 8, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.