Triple
T5207404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinto shrines |
E117544
|
entity |
| Predicate | accessStructure |
P62018
|
FINISHED |
| Object | torii gate |
—
|
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: torii gate | Statement: [Shinto shrines, accessStructure, torii gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessStructure Context triple: [Shinto shrines, accessStructure, torii gate]
-
A.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
B.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
C.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
D.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
E.
accessProvides
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
- F. None of above. chosen
Provenance (4 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a4a7b7c8190af5a7149f8fe4f87 |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79000cf88190b3c05d95395b0cd2 |
completed | March 20, 2026, 4:42 p.m. |
Created at: March 20, 2026, 1:47 p.m.