Triple
T14057490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC Strasbourg Alsace |
E338255
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | RCSA |
E338255
|
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: RCSA | Statement: [RC Strasbourg Alsace, shortName, RCSA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RCSA Context triple: [RC Strasbourg Alsace, shortName, RCSA]
-
A.
RCSA
chosen
RCSA is the commonly used abbreviation for RC Strasbourg Alsace, a professional football club based in Strasbourg, France.
-
B.
RSCS
RSCS (Remote Spooling Communications Subsystem) is an IBM networking protocol used on VM systems to transfer files, messages, and print jobs between computers in a store-and-forward manner.
-
C.
RSCE
RSCE is a United Nations regional administrative and support hub based in Entebbe, Uganda, that provides shared services to UN missions and offices in Africa.
-
D.
RCDS
RCDS is a German student organization aligned with Christian democratic values and politics.
-
E.
R.C.C.S.
R.C.C.S. is the abbreviation for the Royal Canadian Corps of Signals, the former communications branch of the Canadian Army responsible for military signaling and telecommunications.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb662c37c8190a629278a97060080 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:20 p.m.