Triple

T7128438
Position Surface form Disambiguated ID Type / Status
Subject USS Langley (CVL-27) E166124 entity
Predicate serviceEntryInFrenchNavy P34033 FINISHED
Object 1951 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: 1951 | Statement: [USS Langley (CVL-27), serviceEntryInFrenchNavy, 1951]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: serviceEntryInFrenchNavy
Context triple: [USS Langley (CVL-27), serviceEntryInFrenchNavy, 1951]
  • A. fleetCommander (French)
    Indicates that one entity serves as the commanding officer in charge of a fleet associated with another entity.
  • B. serviceEntryWithLuftwaffe
    Indicates that an entity’s service entry or enlistment is associated with the Luftwaffe (the German air force).
  • C. maritimeFunction
    Indicates a relationship where an entity serves a role, purpose, or operational function specifically within maritime contexts such as sea transport, navigation, or marine activities.
  • D. inServiceFrom chosen
    Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
  • E. shipCommissionedAs
    Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
  • 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_69c6888350588190870cd552b427a1cd completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e66b230c819090ddbc5396868305 completed March 27, 2026, 8:19 p.m.
PD Predicate disambiguation batch_69c6e1c7289881909f3b533c384f9ed4 completed March 27, 2026, 8 p.m.
Created at: March 27, 2026, 2:44 p.m.