Triple
T33119787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pumapunku complex |
E847561
|
entity |
| Predicate | stoneSourceRegion |
P410
|
FINISHED |
| Object | quarries near Lake Titicaca |
—
|
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: quarries near Lake Titicaca | Statement: [Pumapunku complex, stoneSourceRegion, quarries near Lake Titicaca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoneSourceRegion Context triple: [Pumapunku complex, stoneSourceRegion, quarries near Lake Titicaca]
-
A.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
B.
bearerRegion
Indicates the geographic or administrative region in which the bearer of something (such as a document, asset, or right) is located or recognized.
-
C.
supplyRegion
Indicates that one entity serves as the source or provider of supplies, goods, or services to a specified geographic region.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d717796c8190a5f4a23056ed7851 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.