Triple
T22919584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC Cola |
E568822
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | RC |
—
|
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: RC | Statement: [RC Cola, shortName, RC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RC Context triple: [RC Cola, shortName, RC]
-
A.
RC
chosen
RC is a brand of cola soft drink, best known as Royal Crown Cola, that serves as a long-standing alternative to major competitors like Coca-Cola and Pepsi.
-
B.
RC
RC is the station code for Raichur railway station, a key rail junction in the Indian state of Karnataka.
-
C.
RCL
RCL is the stock ticker symbol for Royal Caribbean Cruises Ltd., a major global cruise line operator.
-
D.
RLC
RLC is the Royal Logistic Corps, a branch of the British Army responsible for providing logistics support including supply, transport, and distribution.
-
E.
RLC
RLC is a Radio Link Control protocol used in UMTS mobile networks to manage reliable data transfer and segmentation between the radio network and user equipment.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d316188190901d9356c07110e3 |
completed | April 29, 2026, 3:53 a.m. |
Created at: April 17, 2026, 3:42 p.m.