Triple
T478927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca Lines |
E9122
|
entity |
| Predicate | discoveredByModernScience |
P412
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Nazca Lines, discoveredByModernScience, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredByModernScience Context triple: [Nazca Lines, discoveredByModernScience, early 20th century]
-
A.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
B.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
historicallyFormulatedBy
Indicates that something (such as an idea, theory, or document) was originally developed, articulated, or formally established by a particular agent or group in the past.
-
E.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
- 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.