Triple
T11993577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MC Alger |
E285471
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | MCA |
E285470
|
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: MCA | Statement: [MC Alger, shortName, MCA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCA Context triple: [MC Alger, shortName, MCA]
-
A.
MCA
MCA was a major American record label and entertainment company known for signing prominent artists and producing a wide range of popular music releases.
-
B.
MCA
MCA is the UK government executive agency responsible for maritime safety, search and rescue coordination, and preventing pollution from ships in UK waters.
-
C.
MCA
chosen
MCA is a prominent Algerian football club based in Algiers, officially known as Mouloudia Club d'Alger.
-
D.
MCA
MCA is a postgraduate professional degree in computer applications that focuses on advanced software development, programming, and IT skills.
-
E.
MCA
MCA is the national regulatory authority overseeing electronic communications, eCommerce, and postal services in Malta.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903b11ac481909866b611380792e7 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48ad06350819094180403858db172 |
completed | May 1, 2026, 11:13 a.m. |
Created at: April 8, 2026, 9:46 p.m.