Triple
T25070903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin-Fukushima Station |
E627904
|
entity |
| Predicate | hasRetailKiosk |
P49756
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shin-Fukushima Station, hasRetailKiosk, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailKiosk Context triple: [Shin-Fukushima Station, hasRetailKiosk, yes]
-
A.
hasRetailKiosks
chosen
Indicates that one entity operates or maintains retail kiosks associated with or located within another entity.
-
B.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
C.
hasRetailFormat
Indicates that one entity operates or is organized according to a particular retail format or store type.
-
D.
hasRetailProduct
Indicates that an entity offers, sells, or makes available a particular product in a retail context.
-
E.
hasRetailCharacteristic
Indicates that an entity possesses a specific attribute, feature, or quality relevant to retail contexts (such as pricing, packaging, or point-of-sale properties).
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 18, 2026, 6:10 a.m.