Triple

T14209735
Position Surface form Disambiguated ID Type / Status
Subject Australian Plate E352195 entity
Predicate boundaryTypeWith Antarctic Plate P13012 FINISHED
Object divergent boundary 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: divergent boundary | Statement: [Australian Plate, boundaryTypeWith Antarctic Plate, divergent boundary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boundaryTypeWith Antarctic Plate
Context triple: [Australian Plate, boundaryTypeWith Antarctic Plate, divergent boundary]
  • A. plateBoundaryTypeWithAntarcticPlate chosen
    Indicates the type of tectonic plate boundary that exists between the referenced plate and the Antarctic Plate.
  • B. boundaryTypeWithAfricanPlate
    Indicates the type of tectonic plate boundary that exists between a given plate and the African Plate.
  • C. boundaryTypeWithNorthAmericanPlate
    Indicates the type of tectonic plate boundary that exists between a given entity and the North American Plate.
  • D. boundaryTypeWithNazcaPlate
    Indicates the type of tectonic plate boundary that exists between the referenced entity and the Nazca Plate.
  • E. typeOfBoundaryWithEurasianPlate
    Indicates the kind of tectonic plate boundary that exists between a given plate or region and the Eurasian Plate.
  • 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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61fa8d24819092a8ec5d34c1c799 completed April 14, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69de05bcd7d48190a4848d9320404aa6 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:05 a.m.