Triple
T30503193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adventure Galley |
E776193
|
entity |
| Predicate | approximateFateYear |
P195728
|
FINISHED |
| Object | 1698 |
—
|
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: 1698 | Statement: [Adventure Galley, approximateFateYear, 1698]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateFateYear Context triple: [Adventure Galley, approximateFateYear, 1698]
-
A.
approximateProposalYear
Indicates that one entity specifies an estimated or approximate year in which a proposal was made or put forward for the other entity.
-
B.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
C.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
D.
retitleApproxYear
Indicates that an entity was retitled or renamed around an approximate year, rather than at a precisely known date.
-
E.
approximateSettingYear
Indicates the approximate calendar year in which the primary events or setting of something (e.g., a work or scenario) take place.
- F. None of above. chosen
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 29, 2026, 8:15 p.m.