Triple

T1333108
Position Surface form Disambiguated ID Type / Status
Subject Linggadjati Agreement E28687 entity
Predicate recognizedAuthorityOver P13836 FINISHED
Object parts of Java 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: parts of Java | Statement: [Linggadjati Agreement, recognizedAuthorityOver, parts of Java]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizedAuthorityOver
Context triple: [Linggadjati Agreement, recognizedAuthorityOver, parts of Java]
  • A. recognizesAuthority chosen
    Indicates that one entity accepts, acknowledges, or submits to the power, control, or legitimate decision-making role of another entity.
  • B. usesAuthorityOf
    Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
  • C. recognizedRight
    Indicates that an agent formally acknowledges and accepts that another party possesses a specific right or entitlement.
  • D. uniformAuthority
    Indicates that an authority or governing body applies rules, standards, or control consistently and uniformly across all relevant entities or situations.
  • E. recognizedFor
    Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with 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_69a498561a508190a3e1bc137c2b866a completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c1e7f1388190a6e4eb65a7997380 completed March 1, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69a4bef174708190a07bbc697fe19a2d completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:55 p.m.