Triple
T1067873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria (ship) |
E23253
|
entity |
| Predicate | expeditionReturnDate |
P20706
|
FINISHED |
| Object | 1522 |
—
|
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: 1522 | Statement: [Victoria (ship), expeditionReturnDate, 1522]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionReturnDate Context triple: [Victoria (ship), expeditionReturnDate, 1522]
-
A.
expeditionEndYear
chosen
Indicates the calendar year in which an expedition or journey was completed or officially ended.
-
B.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
D.
ultimateFulfillmentAt
Indicates that something reaches its highest or final state of completion, satisfaction, or realization at a specified point, place, or condition.
-
E.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.