Triple
T3069340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Amelia |
E62181
|
entity |
| Predicate | notableIncidentLocation |
P3858
|
FINISHED |
| Object | Dutch colonial waters |
—
|
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: Dutch colonial waters | Statement: [Princess Amelia, notableIncidentLocation, Dutch colonial waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableIncidentLocation Context triple: [Princess Amelia, notableIncidentLocation, Dutch colonial waters]
-
A.
notableLocation
chosen
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableAttackLocation
Indicates the specific place where a significant or notable attack occurred in relation to the subject.
-
C.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
D.
capturedPlace
Indicates that an agent took control of or seized a specific place, typically through force or strategic action.
-
E.
allegedShooterLocation
Indicates the place where a person is claimed or reported to have carried out a shooting.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada100f0b8819095da366fdc6803a8 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.