Triple
T33119785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pumapunku complex |
E847561
|
entity |
| Predicate | approximateLargestBlockWeight |
P198200
|
FINISHED |
| Object | over 100 tonnes |
—
|
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: over 100 tonnes | Statement: [Pumapunku complex, approximateLargestBlockWeight, over 100 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateLargestBlockWeight Context triple: [Pumapunku complex, approximateLargestBlockWeight, over 100 tonnes]
-
A.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
B.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
C.
hasApproximateDifficulty
Indicates that one entity is associated with another entity representing an estimated or non-exact level of difficulty.
-
D.
summitBlockDifficulty
Indicates the level of technical challenge or effort required to reach the summit or highest point of a route or climb.
-
E.
approximateBlockTimeHours
Indicates the estimated number of hours it takes for a block-related event or process to complete.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:27 a.m.