Triple

T2805558
Position Surface form Disambiguated ID Type / Status
Subject Cocos–Nazca spreading center E54044 entity
Predicate isBoundaryType P1972 FINISHED
Object constructive plate margin 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: constructive plate margin | Statement: [Cocos–Nazca spreading center, isBoundaryType, constructive plate margin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBoundaryType
Context triple: [Cocos–Nazca spreading center, isBoundaryType, constructive plate margin]
  • A. hasBoundaryType chosen
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • B. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • C. hasBorderRelation
    Indicates that one entity shares a boundary or border with another entity.
  • D. hasBorderFacilityType
    Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
  • E. boundaryBetween
    Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
  • 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_69ab49dcee188190b5c6eca9ae9e3469 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde2ec2ac8190bd702ad3eafb6aed completed March 7, 2026, 8:13 a.m.
PD Predicate disambiguation batch_69abdd059f308190853191f6ffe2bc6f completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:59 p.m.