Triple

T1765788
Position Surface form Disambiguated ID Type / Status
Subject General E38759 entity
Predicate notTypicallyUsedInBranch P7974 FINISHED
Object navy 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: navy | Statement: [General, notTypicallyUsedInBranch, navy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notTypicallyUsedInBranch
Context triple: [General, notTypicallyUsedInBranch, navy]
  • A. isPartOfBranchTypically
    Indicates that something is typically a component or subdivision within a larger branch.
  • B. notTypicallyUsedFor chosen
    Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
  • C. usedByBranch
    Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
  • D. notObservedIn
    Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
  • E. isUniqueBranchOf
    Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
  • 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_69a8862d562481908d7025a1c1f67c0d completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69ab39fc2c448190bfaf1ee8d474632a completed March 6, 2026, 8:33 p.m.
PD Predicate disambiguation batch_69aa61cbb1288190a7ba38b61905f578 completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:31 p.m.