Triple

T25591077
Position Surface form Disambiguated ID Type / Status
Subject gobernaciones marítimas de Chile E641523 entity
Predicate dependenDe P38982 FINISHED
Object Armada de Chile NE NERFINISHED

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: Armada de Chile | Statement: [gobernaciones marítimas de Chile, dependenDe, Armada de Chile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dependenDe
Context triple: [gobernaciones marítimas de Chile, dependenDe, Armada de Chile]
  • A. dependency chosen
    Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
  • B. crownDependencyOf
    Indicates that one entity is a Crown dependency that is self-governing but under the sovereignty or jurisdiction of another entity (typically a state or monarch).
  • C. fateDependsOn
    Indicates that the outcome or destiny of one entity is determined or significantly influenced by another entity or condition.
  • D. kernelDependsOn
    Indicates that one kernel or core software component requires another kernel or component to be present or available in order to function correctly.
  • E. statusDependsOn
    Indicates that the status or state of one entity is determined or influenced by the status or state of another entity.
  • 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_69e75dc60d108190b7e2419e36b0134b completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f96cc064819088071450af183d1c completed May 2, 2026, 1:17 p.m.
PD Predicate disambiguation batch_69f49377411c8190b2188de444d76795 completed May 1, 2026, 11:50 a.m.
Created at: April 21, 2026, 4:24 p.m.