Triple
T10485380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itsukushima Shrine |
E247280
|
entity |
| Predicate | toriiFeature |
P25751
|
FINISHED |
| Object | stands in the sea and appears to float at high tide |
—
|
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: stands in the sea and appears to float at high tide | Statement: [Itsukushima Shrine, toriiFeature, stands in the sea and appears to float at high tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toriiFeature Context triple: [Itsukushima Shrine, toriiFeature, stands in the sea and appears to float at high tide]
-
A.
hasTorii
chosen
Indicates that something possesses or features a torii gate as part of its structure or environment.
-
B.
toriiDonatedBy
Indicates that a specific torii gate was donated or gifted by a particular person, group, or organization.
-
C.
typicalShrineFeature
Indicates that something is a characteristic or commonly found element of a shrine.
-
D.
numberOfMainTorii
Indicates the specific count of primary torii gates associated with a given entity.
-
E.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5096988ec81908d7518b09256c145 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.