Triple
T478903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca Lines |
E9122
|
entity |
| Predicate | creationMethod |
P625
|
FINISHED |
| Object | removal of surface pebbles to expose lighter subsoil |
—
|
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: removal of surface pebbles to expose lighter subsoil | Statement: [Nazca Lines, creationMethod, removal of surface pebbles to expose lighter subsoil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationMethod Context triple: [Nazca Lines, creationMethod, removal of surface pebbles to expose lighter subsoil]
-
A.
coCreatedWith
Indicates that an entity participated jointly with another entity in the creation or production of something.
-
B.
constructionMethod
chosen
Indicates the technique or process by which something is built, assembled, or created.
-
C.
coCreator
Indicates that two or more entities jointly created or produced something together.
-
D.
foundingMethod
Indicates the way or process by which an entity (such as an organization, institution, or settlement) was originally established or created.
-
E.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.