Triple
T383814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1611 Hudson Bay mutiny |
E8735
|
entity |
| Predicate | chronologyWithinWork |
P5172
|
FINISHED |
| Object | fourth voyage of Henry Hudson |
—
|
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: fourth voyage of Henry Hudson | Statement: [1611 Hudson Bay mutiny, chronologyWithinWork, fourth voyage of Henry Hudson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyWithinWork Context triple: [1611 Hudson Bay mutiny, chronologyWithinWork, fourth voyage of Henry Hudson]
-
A.
workChronologyPosition
chosen
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
D.
dateOfComposition
Indicates the calendar date or time period when a particular work was created or composed.
-
E.
occurredIn
Indicates that an event or action took place within a specific location, context, or time frame.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec422b808190b6ddf747ef939151 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.