Triple

T7605701
Position Surface form Disambiguated ID Type / Status
Subject Japanese carrier Chitose E180097 entity
Predicate typeAfterConversion P71588 FINISHED
Object light aircraft carrier 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: light aircraft carrier | Statement: [Japanese carrier Chitose, typeAfterConversion, light aircraft carrier]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeAfterConversion
Context triple: [Japanese carrier Chitose, typeAfterConversion, light aircraft carrier]
  • A. typeAfterRefit chosen
    Indicates that an entity’s type or classification after undergoing a refit or modification is the specified value.
  • B. functionAfterConversion
    Indicates that one function or behavior occurs as a result of, or is valid only after, a specified conversion has taken place.
  • C. locationAfterConversion
    Indicates the place or position an entity occupies after it has been transformed, converted, or changed from one state or form to another.
  • D. methodOfConversion
    Indicates the specific process or technique used to transform one form, state, or representation into another.
  • E. allowsConversionTo
    Indicates that one entity permits or enables transformation or change into another specified form or state.
  • 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_69c69f3567008190ab01d2ca7b53584a completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c6f9fcfcfc8190a29a0b5cd3e8927a completed March 27, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69c6f4e485f88190910b39da52a955fe completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:54 p.m.