Triple
T36416099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish passports |
E897006
|
entity |
| Predicate | chipStores |
P63988
|
FINISHED |
| Object | facial image |
—
|
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: facial image | Statement: [Swedish passports, chipStores, facial image]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chipStores Context triple: [Swedish passports, chipStores, facial image]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
reportedlyStores
Indicates that an entity is said or believed, based on reports or claims, to store or hold another entity, without confirming that this storage actually occurs.
-
C.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
D.
store
chosen
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
E.
storefront
Indicates the physical or virtual front-facing location where a business presents and offers its goods or services to customers.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.