Triple

T34400384
Position Surface form Disambiguated ID Type / Status
Subject SS Empress of Canada (2029) E882961 entity
Predicate isPlannedBuilder P179382 FINISHED
Object John Brown & Company NE NERFINISHED

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: John Brown & Company | Statement: [SS Empress of Canada (2029), isPlannedBuilder, John Brown & Company]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPlannedBuilder
Context triple: [SS Empress of Canada (2029), isPlannedBuilder, John Brown & Company]
  • A. isPlannedThrough
    Indicates that something is intended to be achieved, organized, or carried out by means of a specified plan, method, or intermediary process.
  • B. isPlannedAround
    Indicates that one entity is organized, scheduled, or structured with consideration of, or in alignment with, another entity as a central reference or constraint.
  • C. plannedIn
    Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
  • D. isPlannedCity
    Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
  • E. plannedWith
    Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
  • F. None of above. chosen

Provenance (4 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_69f349c1304081909331872829e38106 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f720cc1bfc8190a16118e3af8e9316 completed May 3, 2026, 10:17 a.m.
PD Predicate disambiguation batch_69f71cc6397881909aaad37a9daa8a7e completed May 3, 2026, 10 a.m.
PDg Predicate description generation batch_69f71fb0172c81908f23e95ff16b0dec completed May 3, 2026, 10:13 a.m.
Created at: May 1, 2026, 1:59 a.m.