Triple

T3272074
Position Surface form Disambiguated ID Type / Status
Subject France 3 E68669 entity
Predicate regulator P46 FINISHED
Object ARCOM E331156 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: ARCOM | Statement: [France 3, regulator, ARCOM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARCOM
Context triple: [France 3, regulator, ARCOM]
  • A. ARCOM chosen
    ARCOM is the French regulatory authority overseeing audiovisual and digital communication, created to succeed and expand the role of the former Conseil supérieur de l’audiovisuel.
  • B. ARC
    ARC is a family of configurable 32-bit RISC processor architectures commonly used in embedded and SoC designs.
  • C. ARC
    ARC is the commonly used acronym for the Augmentation Research Center, a pioneering research group known for its early work on interactive computing and human–computer interaction.
  • D. ARCX
    ARCX is the Market Identifier Code for the NYSE Arca exchange, an electronic securities trading platform operated by the New York Stock Exchange.
  • E. AMRO
    AMRO is the World Health Organization’s Regional Office responsible for public health leadership and coordination across the Americas.
  • 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_69ad859b54f881909bf530d549caf2fd completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adaff6308881908886a44804a0bb09 completed March 8, 2026, 5:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69b28f0793e08190af55ee16e5091451 completed March 12, 2026, 10:01 a.m.
Created at: March 8, 2026, 3:10 p.m.