Triple
T21214384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian Regional Commission |
E522798
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | ARC |
—
|
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: ARC | Statement: [Appalachian Regional Commission, shortName, ARC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ARC Context triple: [Appalachian Regional Commission, shortName, ARC]
-
A.
ARC
ARC is a U.S. federal farm safety net program that provides income support to agricultural producers when their revenue or crop prices fall below guaranteed levels.
-
B.
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.
-
C.
ARC
ARC is a family of configurable 32-bit RISC processor architectures commonly used in embedded and SoC designs.
-
D.
ARC
chosen
ARC is a U.S. federal–state regional economic development agency focused on improving economic growth and quality of life in the Appalachian region.
-
E.
ARC
ARC is the official abbreviation used to designate ships and assets of the Colombian Navy (Armada de la República de Colombia).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734727a30819089c433e4fe6f438a |
completed | April 21, 2026, 8:25 a.m. |
Created at: April 16, 2026, 3:39 p.m.