Triple
T26014490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraca Valley |
E646987
|
entity |
| Predicate | hasNearbySacredSite |
P61457
|
FINISHED |
| Object | Sun Temple of Sogamoso |
—
|
NE NERFINISHED |
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: Sun Temple of Sogamoso | Statement: [Iraca Valley, hasNearbySacredSite, Sun Temple of Sogamoso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySacredSite Context triple: [Iraca Valley, hasNearbySacredSite, Sun Temple of Sogamoso]
-
A.
hasNearbyPilgrimageSite
chosen
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
B.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
C.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
-
D.
hasNearbyMonasteryLandingPoints
Indicates that there are designated landing points located close to a monastery.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 9:03 a.m.