Triple
T13490559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ePassport |
E318620
|
entity |
| Predicate | dataStoredOnChipIs |
P1596
|
FINISHED |
| Object | digitally signed |
—
|
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: digitally signed | Statement: [ePassport, dataStoredOnChipIs, digitally signed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataStoredOnChipIs Context triple: [ePassport, dataStoredOnChipIs, digitally signed]
-
A.
displayChip
Indicates that one entity presents or renders another entity as a chip-style visual element in a user interface.
-
B.
hasOnChipCache
Indicates that one hardware component includes an integrated cache memory directly on the same chip.
-
C.
dataStorage
chosen
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
D.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
E.
builtInMemoryOf
Indicates that something was constructed as a tribute or commemoration to a particular person, group, or event.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3cbe2081908c6792362c67c8f1 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.