Triple

T15924153
Position Surface form Disambiguated ID Type / Status
Subject RBE2-AA E386164 entity
Predicate manufacturer P490 FINISHED
Object Thales Group E81227 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: Thales Group | Statement: [RBE2-AA, manufacturer, Thales Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thales Group
Context triple: [RBE2-AA, manufacturer, Thales Group]
  • A. Thales Group chosen
    Thales Group is a French multinational company specializing in aerospace, defense, security, and transportation technologies and systems.
  • B. Polytech Group
    Polytech Group is a French network of public university engineering schools offering accredited engineering degrees across a wide range of specialties.
  • C. Thales Nederland
    Thales Nederland is the Dutch branch of the Thales Group, specializing in high-tech defense, security, and radar systems.
  • D. Industree Group
    Industree Group is a company that has acquired commercial naming rights to sports and entertainment venues, including Industree Group Stadium in Australia.
  • E. Tractebel
    Tractebel is an international engineering and consulting company specializing in energy, water, and infrastructure projects.
  • 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_69d86da750008190987eb26be3f6c118 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1568424f08190bffe6ee465a0db9a completed April 16, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffe46b06688190a02fee3700efd709 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:52 a.m.