Triple

T36717897
Position Surface form Disambiguated ID Type / Status
Subject Māori incorporations E906962 entity
Predicate canBorrow P7921 FINISHED
Object money for development projects 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: money for development projects | Statement: [Māori incorporations, canBorrow, money for development projects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBorrow
Context triple: [Māori incorporations, canBorrow, money for development projects]
  • A. canBorrowFrom
    Indicates that one entity is permitted or able to borrow something (such as resources, items, or privileges) from another entity.
  • B. canBring
    Indicates that one entity has the ability or permission to bring another entity or item to a particular place or context.
  • C. canPayFor
    Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
  • D. canEarnOn
    Indicates that an entity is able or permitted to receive or generate earnings from another entity, source, or activity.
  • E. eligibleBorrower chosen
    Indicates that an entity meets the required conditions to be allowed to borrow (e.g., money, items, or resources) under a given set of rules or policies.
  • 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_69f76e73ad108190a5241585f2303e9a completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c841388481909a408b704b30f9c7 completed May 3, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69f7c4796ebc819084a0dc08505e5f14 completed May 3, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:12 p.m.