Triple

T10624419
Position Surface form Disambiguated ID Type / Status
Subject Compagnie Universelle du Canal Interocéanique de Panama E250284 entity
Predicate engineeringConcept P54422 FINISHED
Object sea-level canal 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: sea-level canal | Statement: [Compagnie Universelle du Canal Interocéanique de Panama, engineeringConcept, sea-level canal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: engineeringConcept
Context triple: [Compagnie Universelle du Canal Interocéanique de Panama, engineeringConcept, sea-level canal]
  • A. technologyConcept chosen
    Indicates a relationship where one entity represents or embodies a technological idea, principle, or method conceptually associated with another entity.
  • B. engineeringFeature
    Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
  • C. engineeringEmphasis
    Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
  • D. mechanicalDesign
    Indicates that one entity is responsible for or associated with the mechanical design or engineering configuration of another entity.
  • E. engineeringGoal
    Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df7fe9fc81908b3b8d1dc06a829c completed April 8, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69d6dd7fae088190973f70c69738af49 completed April 8, 2026, 10:58 p.m.
Created at: April 8, 2026, 8:53 p.m.