Triple

T19006107
Position Surface form Disambiguated ID Type / Status
Subject Fortune E465087 entity
Predicate voyageSequenceRelativeToMayflower P35334 FINISHED
Object second ship to reach Plymouth Colony 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: second ship to reach Plymouth Colony | Statement: [Fortune, voyageSequenceRelativeToMayflower, second ship to reach Plymouth Colony]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: voyageSequenceRelativeToMayflower
Context triple: [Fortune, voyageSequenceRelativeToMayflower, second ship to reach Plymouth Colony]
  • A. maidenVoyageRoute
    Indicates the route or path taken by something (typically a vessel or vehicle) on its first official journey or inaugural trip.
  • B. relativeToJamestown
    Indicates a spatial or contextual relationship defined in terms of Jamestown as the reference point.
  • C. sequenceInBeagleVoyages
    Indicates that one event, observation, or item occurs at a specific position within the ordered sequence of Beagle voyages.
  • D. famousVoyage
    Indicates that a voyage is widely recognized or celebrated for its historical, cultural, or exploratory significance.
  • E. subsequentVoyage chosen
    Indicates that one voyage occurs after and in sequence to another voyage in time.
  • 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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6a494688190a277b2cddf300235 completed April 20, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69e4a2f88e0c81908cb20f08bf24cd32 completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:01 p.m.