Triple
T36149259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omotesando crossing |
E1045538
|
entity |
| Predicate | typicalSignage |
—
|
GENERATED |
| Object | bilingual Japanese-English signs |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSignage Context triple: [Omotesando crossing, typicalSignage, bilingual Japanese-English signs]
-
A.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
B.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
C.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
D.
hasSignageType
chosen
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
E.
usedAsSignage
Indicates that something is employed as a sign or display to convey information, directions, warnings, or identification.
- F. None of above.
Provenance (1 batch)
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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.