Triple
T19293311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Ship disaster |
E482494
|
entity |
| Predicate | intendedRoute |
P91689
|
FINISHED |
| Object | Barfleur to England |
—
|
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: Barfleur to England | Statement: [White Ship disaster, intendedRoute, Barfleur to England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRoute Context triple: [White Ship disaster, intendedRoute, Barfleur to England]
-
A.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
B.
hadRoute
chosen
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
C.
approachRoute
Indicates the path or method taken by one entity as it moves toward or comes closer to another entity or target.
-
D.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
E.
routePurpose
Indicates the intended function or goal that a particular route is designed or used to serve.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc824b448190865230eed8ef9ebf |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.