Triple
T18540566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whangaroa Harbour |
E453086
|
entity |
| Predicate | Boyd incident |
P76024
|
FINISHED |
| Object | occurred in 1809 |
—
|
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: occurred in 1809 | Statement: [Whangaroa Harbour, Boyd incident, occurred in 1809]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Boyd incident Context triple: [Whangaroa Harbour, Boyd incident, occurred in 1809]
-
A.
falklandsWarIncident
Indicates an event or occurrence that took place as part of, or in direct connection with, the Falklands War.
-
B.
Tambov Rebellion
Indicates an organized uprising or revolt occurring in or associated with Tambov, typically involving armed resistance against an established authority.
-
C.
accusationByBlockadingStates
Indicates that certain states enforcing a blockade are the ones making an accusation against another party.
-
D.
notableIncidentType
chosen
Indicates the specific category or kind of significant event or incident associated with an entity.
-
E.
Columbia disaster
Indicates the relationship of being involved in, affected by, or causally connected to the Space Shuttle Columbia disaster 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b64178819082861a03fd067095 |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.