Triple
T27800081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geku (Outer Shrine) |
E702214
|
entity |
| Predicate | hasSacredBoundary |
P100085
|
FINISHED |
| Object | fence and torii demarcating holy area |
—
|
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: fence and torii demarcating holy area | Statement: [Geku (Outer Shrine), hasSacredBoundary, fence and torii demarcating holy area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredBoundary Context triple: [Geku (Outer Shrine), hasSacredBoundary, fence and torii demarcating holy area]
-
A.
sacredBoundary
chosen
Indicates a boundary that is regarded as holy or inviolable and therefore must not be crossed, altered, or violated.
-
B.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
-
C.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
D.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
E.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 5:33 p.m.