Triple
T33332140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguirre, der Zorn Gottes |
E853435
|
entity |
| Predicate | setInRiver |
P73621
|
FINISHED |
| Object | Amazon River |
—
|
NE NERFINISHED |
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: Amazon River | Statement: [Aguirre, der Zorn Gottes, setInRiver, Amazon River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInRiver Context triple: [Aguirre, der Zorn Gottes, setInRiver, Amazon River]
-
A.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
B.
locatedInRiverArea
chosen
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
C.
plannedOnRiver
Indicates that something is intended or designed to be located, constructed, or carried out on or along a river.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
operatesOnRiver
Indicates that an entity conducts its operations or activities on, along, or directly involving a river.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:34 a.m.