Triple
T27800054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geku (Outer Shrine) |
E702214
|
entity |
| Predicate | hasSacredPrecinct |
P170654
|
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: [Geku (Outer Shrine), hasSacredPrecinct, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredPrecinct Context triple: [Geku (Outer Shrine), hasSacredPrecinct, yes]
-
A.
hasCultPlaceType
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
B.
hasSpiritualSitesIn
Indicates that one entity possesses or contains spiritual or religious sites located within the boundaries of another entity.
-
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.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 5:33 p.m.