Triple
T11577679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choquequirao |
E274547
|
entity |
| Predicate | percentageExcavated |
P48450
|
FINISHED |
| Object | partially excavated |
—
|
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: partially excavated | Statement: [Choquequirao, percentageExcavated, partially excavated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: percentageExcavated Context triple: [Choquequirao, percentageExcavated, partially excavated]
-
A.
excavatedFor
Indicates that something has been dug out or uncovered from the ground specifically for the benefit, use, or purpose of another entity.
-
B.
excavatedVolume
Indicates the amount of material removed from a site or area as a result of an excavation activity.
-
C.
excavated
Indicates that one entity has dug out, uncovered, or removed earth or material from another entity, typically to reveal or extract what lies beneath.
-
D.
excavationStatus
chosen
Indicates the current state or phase of an excavation activity, such as whether it is planned, in progress, paused, or completed.
-
E.
excavatedAfter
Indicates that one excavation event occurred later in time than another excavation event.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89049721081909278adfada668ef9 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.