Triple
T13857237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France Info (radio) |
E333096
|
entity |
| Predicate | regulatedBy |
P86
|
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 Info (radio), regulatedBy, ARCOM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ARCOM Context triple: [France Info (radio), regulatedBy, 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 official abbreviation used to designate ships and assets of the Colombian Navy (Armada de la República de Colombia).
-
D.
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.
-
E.
ARC
ARC is the Atlanta Regional Commission, a regional planning and intergovernmental coordination agency serving the metropolitan Atlanta area.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70a59e8819090b750699993a107 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:14 p.m.