Triple
T8938863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charisma Records |
E212845
|
entity |
| Predicate | distributedBy |
P1951
|
FINISHED |
| Object | WEA |
E117366
|
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: WEA | Statement: [Charisma Records, distributedBy, WEA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WEA Context triple: [Charisma Records, distributedBy, WEA]
-
A.
WEA
WEA is a U.S. nationwide public safety system that delivers government-issued emergency alerts to compatible mobile devices.
-
B.
WEA
WEA is the acronym for the World Evangelical Alliance, a global network that connects and represents evangelical churches and organizations worldwide.
-
C.
WEA Inc.
chosen
WEA Inc. was the former distribution and marketing arm of Warner Music Group, handling the global release of the company’s recorded music.
-
D.
WECA
WECA is the former name of the Wi‑Fi Alliance, the global industry consortium that develops and certifies Wi‑Fi standards and interoperability.
-
E.
WAE
WAE is the National Rail station code for Waterloo East railway station in London, England.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b7484481909e0d7610552f5386 |
completed | April 1, 2026, 12:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1eb308c81909f5be133c75ad568 |
completed | April 3, 2026, 1:34 p.m. |
Created at: March 30, 2026, 6:58 p.m.