Triple
T14923990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albanian passports |
E371584
|
entity |
| Predicate | introducedAsBiometric |
P63130
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Albanian passports, introducedAsBiometric, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsBiometric Context triple: [Albanian passports, introducedAsBiometric, 2009]
-
A.
includesBiometrics
chosen
Indicates that one entity contains, uses, or is associated with biometric data or biometric identifiers of another entity.
-
B.
hasFingerprintSensor
Indicates that an entity is equipped with or includes a fingerprint recognition sensor.
-
C.
hasFaceUnlock
Indicates that an entity supports or is equipped with a facial recognition–based unlocking feature.
-
D.
hasProcessOfRecognition
Indicates that one entity is involved in or characterized by a process of recognizing, identifying, or acknowledging another entity or condition.
-
E.
recognizedFeature
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or context.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6323f8c8190af02d06352d459c3 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:34 a.m.