Triple

T23915969
Position Surface form Disambiguated ID Type / Status
Subject Finisterre–Huon languages E602081 entity
Predicate arePrimarilyUsedFor P125948 FINISHED
Object local communication 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: local communication | Statement: [Finisterre–Huon languages, arePrimarilyUsedFor, local communication]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: arePrimarilyUsedFor
Context triple: [Finisterre–Huon languages, arePrimarilyUsedFor, local communication]
  • A. isPrimarilyUsedAs chosen
    Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
  • B. primaryUseOf
    Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
  • C. usedPrimarilyIn
    Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
  • D. laterPrimarilyUsedFor
    Indicates that something was initially used for one purpose but, at a later time, came to be used mainly for another specified purpose.
  • E. appliedPrimarilyTo
    Indicates that something is used mainly or chiefly in relation to a particular target, context, or purpose, rather than being used broadly or equally elsewhere.
  • 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_69e2953a187081908346a9f36e85fc98 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1ce9917808190ad66a4e276a24b3d completed April 29, 2026, 9:25 a.m.
PD Predicate disambiguation batch_69f16151ebdc819086e9e1d7cc1f4f3c completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:40 p.m.