Triple
T15540514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clermont |
E370461
|
entity |
| Predicate | firstVoyageStartDate |
P45302
|
FINISHED |
| Object | 1807-08-17 |
—
|
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: 1807-08-17 | Statement: [Clermont, firstVoyageStartDate, 1807-08-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVoyageStartDate Context triple: [Clermont, firstVoyageStartDate, 1807-08-17]
-
A.
firstVoyageEndYear
Indicates the calendar year in which an entity’s first voyage or initial journey was completed or came to an end.
-
B.
maidenVoyageStartDate
chosen
Indicates the calendar date on which something (typically a vessel or vehicle) undertakes its first official voyage or operational journey.
-
C.
firstChartedOn
Indicates that an entity was first mapped, recorded, or charted on a specific date or during a specific time.
-
D.
voyageStartYearDescribed
Indicates the year in which a voyage is described as having started.
-
E.
firstEuropeanLandingDate
Indicates the date on which Europeans first arrived at or made landfall in a particular place.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:07 a.m.