Triple
T21787542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Pérouse expedition |
E537878
|
entity |
| Predicate | lastDepartureDate |
P96319
|
FINISHED |
| Object | 1788-03-10 |
—
|
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: 1788-03-10 | Statement: [La Pérouse expedition, lastDepartureDate, 1788-03-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastDepartureDate Context triple: [La Pérouse expedition, lastDepartureDate, 1788-03-10]
-
A.
departureDateOnFinalVoyage
chosen
Indicates the date on which an entity began its final voyage or last recorded journey.
-
B.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
C.
lastShuttleFlightDate
Indicates the calendar date on which the most recent shuttle flight associated with the subject took place.
-
D.
departureYear
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
-
E.
lastFlightWith
Indicates that one flight is the most recent flight taken by or associated with a given entity in relation to another entity or context.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621c68588190977891055e80a499 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.