Triple
T5890171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGI |
E130968
|
entity |
| Predicate | usesBiometricModality |
P63130
|
FINISHED |
| Object | fingerprints |
—
|
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: fingerprints | Statement: [NGI, usesBiometricModality, fingerprints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBiometricModality Context triple: [NGI, usesBiometricModality, fingerprints]
-
A.
includesBiometrics
chosen
Indicates that one entity contains, uses, or is associated with biometric data or biometric identifiers of another entity.
-
B.
hasFaceUnlock
Indicates that an entity supports or is equipped with a facial recognition–based unlocking feature.
-
C.
hasFingerprintSensor
Indicates that an entity is equipped with or includes a fingerprint recognition sensor.
-
D.
usesModality
Indicates that an action, communication, or process is carried out through or characterized by a particular modality (such as visual, auditory, tactile, or another mode of expression or operation).
-
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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.