Triple

T15434071
Position Surface form Disambiguated ID Type / Status
Subject Monon Railroad E369712 entity
Predicate reportingMark P2130 FINISHED
Object CIL E1155905 NE 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: CIL | Statement: [Monon Railroad, reportingMark, CIL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CIL
Context triple: [Monon Railroad, reportingMark, CIL]
  • A. CIL
    CIL is the standard scholarly abbreviation for the Corpus Inscriptionum Latinarum, the comprehensive collection of ancient Latin inscriptions.
  • B. CIL
    CIL is the abbreviation for the Committee on Import Licensing, a World Trade Organization body that oversees and reviews members’ import licensing procedures to ensure they are transparent and consistent with WTO rules.
  • C. CIL
    CIL is the low-level, platform-independent bytecode language used by the .NET framework to represent compiled programs before just-in-time compilation.
  • D. CIL chosen
    CIL is the reporting mark used to identify the Monon Railroad, a historic Midwestern U.S. railroad line.
  • E. CIL I
    CIL I is the first volume of the Corpus Inscriptionum Latinarum, containing a foundational collection of early Latin inscriptions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03eda01cc8190843e23b260b8503c completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff21a3d1f481908f6795656514b2b4 completed May 9, 2026, 11:59 a.m.
Created at: April 10, 2026, 3:21 a.m.