Triple

T7174585
Position Surface form Disambiguated ID Type / Status
Subject Paris Gun E167286 entity
Predicate shellNumbering P22578 FINISHED
Object shells were numbered and matched to barrel wear 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: shells were numbered and matched to barrel wear | Statement: [Paris Gun, shellNumbering, shells were numbered and matched to barrel wear]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shellNumbering
Context triple: [Paris Gun, shellNumbering, shells were numbered and matched to barrel wear]
  • A. frontNumbering
    Indicates that an entity is assigned a numbering or label that appears at the front or beginning of something (e.g., a sequence, document, or list).
  • B. numberingType
    Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
  • C. isNumbered chosen
    Indicates that an entity has been assigned a specific number or position in an ordered sequence.
  • D. isNumberedBy
    Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
  • E. standardNumberingScheme
    Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
  • 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_69c68889a2748190a316c5e65360361a completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e9b045c48190b27b2d6f7c11026f completed March 27, 2026, 8:33 p.m.
PD Predicate disambiguation batch_69c6e74fb0f48190b2ad4dd4efdd241a completed March 27, 2026, 8:23 p.m.
Created at: March 27, 2026, 2:48 p.m.