Triple
T1936529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Touch ID |
E41454
|
entity |
| Predicate | fallbackMethod |
P19868
|
FINISHED |
| Object | passcode |
—
|
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: passcode | Statement: [Touch ID, fallbackMethod, passcode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallbackMethod Context triple: [Touch ID, fallbackMethod, passcode]
-
A.
alternativeLaunchMethod
Indicates that there exists a different or non-standard method by which the launch of something can be carried out.
-
B.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
C.
notImplementedBy
Indicates that a specified functionality, specification, or feature is *not* realized or provided by the referenced entity (such as a system, component, or implementation).
-
D.
propagationMethod
Indicates the means or mechanism by which something spreads, reproduces, or is transmitted from one entity or location to another.
-
E.
alternativeRoute
chosen
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c5f6e481909b2d95861e2098f9 |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.