Triple
T7642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayflower landing at Plymouth |
E151
|
entity |
| Predicate | causeOfChangeOfDestination |
P886
|
FINISHED |
| Object | navigational difficulties |
—
|
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: navigational difficulties | Statement: [Mayflower landing at Plymouth, causeOfChangeOfDestination, navigational difficulties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfChangeOfDestination Context triple: [Mayflower landing at Plymouth, causeOfChangeOfDestination, navigational difficulties]
-
A.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
B.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
C.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
D.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
E.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a241a55ac081909e95b71c97db8140 |
completed | Feb. 28, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69a23fe1cf38819080ea56c40bf2632e |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a241a4a0f481908de66b64c6262fcd |
completed | Feb. 28, 2026, 1:15 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.