Triple
T27800050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geku (Outer Shrine) |
E702214
|
entity |
| Predicate | rebuildingCycle |
P144165
|
FINISHED |
| Object | approximately every 20 years |
—
|
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: approximately every 20 years | Statement: [Geku (Outer Shrine), rebuildingCycle, approximately every 20 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildingCycle Context triple: [Geku (Outer Shrine), rebuildingCycle, approximately every 20 years]
-
A.
rebuiltOnCycle
Indicates that an entity is reconstructed or restored during a specified recurring cycle or iteration.
-
B.
rebuildingCycleYears
chosen
Indicates the number of years that typically pass between successive rebuilding or reconstruction cycles of something.
-
C.
rebuiltEvery
Indicates that one entity is reconstructed or built anew at regular intervals defined by another entity.
-
D.
rebuildPeriod
Indicates the time span during which something is reconstructed or restored after damage, failure, or decommissioning.
-
E.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
- 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_69f6380de8908190bbeb5fd0e5bb80ab |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:33 p.m.